We were initializing the segment client 2x - once in App.tsx and once in AppRegistry, the identify call was happening during auth flow so when segment client was reinitialized it blew away the saved user id. Seems only became a problem after the update to the analytics library.
PR Checklist
[ ] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
This PR resolves PHIRE-1082
Description
We were initializing the segment client 2x - once in App.tsx and once in AppRegistry, the identify call was happening during auth flow so when segment client was reinitialized it blew away the saved user id. Seems only became a problem after the update to the analytics library.
PR Checklist
To the reviewers 👀
Changelog updates
### Changelog updates #### Cross-platform user-facing changes - #### iOS user-facing changes - #### Android user-facing changes - #### Dev changes - fix analytics not being tied to user ids - brianNeed help with something? Have a look at our docs, or get in touch with us.