The migration from @expo-analytics-amplitude forces us to eject?

[mikealche]

Hey there!

As @expo-analytics-amplitude is now deprecated, the only two possibilities are this library and this other one

BUT! Both require us to do "pod install"....

Am I not seeing something or to continue using amplitude will will need to eject the app from expo?

[yuhao900914]

Hi @mikealche, thanks for choosing amplitude.
This react-native does not support expo. The new amplitude react-native SDK does support expo. This is an example app you can take a look at.
https://github.com/amplitude/Amplitude-TypeScript/tree/main/examples/react-native/expo-app

Please open an issue in the other repo and provide the details about how we can reproduce it and the error message you have.
Thanks.

[mblarsen]

@mikealche please note that the way @expo-analytics-amplitude is set up for Android there might an issue for you when migrating. To be fully compatible with the expo library you need to set the instanceName property to the value of your old API key. If you do not a new device id (thus user) will be generated and you will loose all your old data for existing users.

Also note, if you have had one app release with the new https://github.com/amplitude/Amplitude-TypeScript/tree/v1.x/packages/analytics-react-native without the instanceName set, setting it in the future has no effect. You can only migrate from expo module to the new plugin with the instanceName set.