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
I updated my segment analytics to the swift version from Obj-c using SPM.
After updating I cannot find 'SEGAnalyticsIntegrationDidStart' in the scope, so after some research I found I should be using this string literal "io.segment.analytics.integration.did.start"
But after using that my observer function is not being called, previously before migration it was called with this "SEGAnalyticsIntegrationDidStart" notification
To Reproduce
use the "io.segment.analytics.integration.did.start" as an observer and its callback will not be called as it suppose to be called
Expected behavior
This selector function(integrationDidStart()) should call if I have added the observer("io.segment.analytics.integration.did.start") correctly.
Platform (please complete the following information):
Library Version in use: 1.5.1
Platform being tested: iOS
Integrations in use: Segment analytics with desitination firebase, adjust, braze
The text was updated successfully, but these errors were encountered:
Describe the bug
I updated my segment analytics to the swift version from Obj-c using SPM.
After updating I cannot find 'SEGAnalyticsIntegrationDidStart' in the scope, so after some research I found I should be using this string literal "io.segment.analytics.integration.did.start"
But after using that my observer function is not being called, previously before migration it was called with this "SEGAnalyticsIntegrationDidStart" notification
To Reproduce
use the "io.segment.analytics.integration.did.start" as an observer and its callback will not be called as it suppose to be called
Expected behavior
This selector function(integrationDidStart()) should call if I have added the observer("io.segment.analytics.integration.did.start") correctly.
Platform (please complete the following information):
The text was updated successfully, but these errors were encountered: