You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The session ID is not being linked properly with amplitude.
To Reproduce
Steps to reproduce the behavior:
Integrate Amplitude plugin by following the examples
Track some events
In amplitude, see that the events are not being logged with a valid session id, even though it is being set within the AmplitudeSession plugin. All the session ids are -1.
Expected behavior
events should be connected via a session id, right now they are not connected.
Screenshots
If applicable, add screenshots to help explain your problem.
Platform (please complete the following information):
Library Version in use: Analytics-Swift 1.6.1, Analytics-Swift-Amplitude 1.4.3
Platform being tested: iOS
Integrations in use: Amplitude
Additional context
Amplitude also indicates that these events are being sent by WebKit605, but they are coming from the SDK.
The text was updated successfully, but these errors were encountered:
The amplitude session plugin (Analytics-Swift-Amplitude) sends the amplitude sessionID to segment, and the data is then sent from segment to amplitude, not from the SDK itself. Since I can't view your workspace to troubleshoot and it's not an analytics-swift issue, I'd recommend you reach out to [email protected] for support. Feel free to reference this ticket when talking to them.
Describe the bug
The session ID is not being linked properly with amplitude.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
events should be connected via a session id, right now they are not connected.
Screenshots
If applicable, add screenshots to help explain your problem.
Platform (please complete the following information):
Additional context
Amplitude also indicates that these events are being sent by WebKit605, but they are coming from the SDK.
The text was updated successfully, but these errors were encountered: