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
We found there is major data discrepancy between our Android and iOS app using Segment and some iOS clients don't report any data to Segment. After investigation, we found that the library will not report any events if the first call to cdn-settings.segment.com fails.
We are using analytics-react-native and it passes an empty dict for defaultSettings.
// don't configure edge functions here. it'll do the right thing on it's own.
} else {
newSettings[@"integrations"][@"Segment.io"][@"apiKey"] doesn't do anything because the keys don't exist. This results in an empty setting cached in the client and no events will be send to Segment.io because the integration is not enabled.
No settings for Segment.io. Skipping.
The text was updated successfully, but these errors were encountered:
We found there is major data discrepancy between our Android and iOS app using Segment and some iOS clients don't report any data to Segment. After investigation, we found that the library will not report any events if the first call to
cdn-settings.segment.com
fails.We are using
analytics-react-native
and it passes an empty dict fordefaultSettings
.https://github.com/segmentio/analytics-react-native/blob/9b5734d58b3f4099b5396504debb4ffad2abdd79/packages/core/src/configuration.ts#L29
This breaks the fallback logic of the library settings because here the code only checks for
nil
.analytics-ios/Segment/Internal/SEGIntegrationsManager.m
Lines 463 to 470 in 9cab023
newSettings[@"integrations"][@"Segment.io"][@"apiKey"]
doesn't do anything because the keys don't exist. This results in an empty setting cached in the client and no events will be send to Segment.io because the integration is not enabled.The text was updated successfully, but these errors were encountered: