Incompatible anonymous ids

[RohovDmytro]

Latest segment version generates anonymous id which is not compatible with anonymous id of MixPanel.

[jparksecurity]

I got the same error on Android and iOS. However, it happens to me only if I use expo run or expo start --dev-client.

It works on the build.

Working(build)

iOS Not working

Android Not working

My environment is

├─ @segment/analytics-react-native@2.7.1
└─ @segment/sovran-react-native@0.4.4

[RohovDmytro]

Yeah, the dev and release build use different mechanism of generating anonymous id. The proposal is to at least unify the format of the string.

[oscb]

Seems like we only had the DEV behavior due to an old RN bug that has already been fixed. I'll remove it in the next release.

[oscb]

🎉 This issue has been resolved in version @segment/analytics-react-native-v2.9.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[willdawsonme]

This change breaks the ability to use the javascript debugger. As soon as the debugger is activated, I get the aforementioned react-native error: facebook/react-native#26705. There's some relevant discussion over at react-native-device-info: react-native-device-info/react-native-device-info#776.

Is there a way to make this UUID call asynchronous so consumers can use the debugger?

[oscb]

What version of RN are you using?On Nov 11, 2022, at 11:40, Will Dawson ***@***.***> wrote: This change breaks the ability to use the javascript debugger. As soon as the debugger is activated, I get the aforementioned react-native error: facebook/react-native#26705. There's some relevant discussion over at react-native-device-info: react-native-device-info/react-native-device-info#776. Is there a way to make this UUID call asynchronous so consumers can use the debugger? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you modified the open/close state.Message ID: ***@***.***>