2.x -> 3.x
UpdatedVersion 3.0.0 of the Customer.io Expo plugin requires the React Native new architecture.
What changed?
Version 3.0.0 removes support for React Native’s legacy architecture. This aligns with React Native’s move to exclusively support their new architecture. You must migrate your app to use React Native’s new architecture to use this and future versions of the plugin.
Do you need to update to this version?
We recommend updating to the latest plugin version. However, if your app uses the old React Native architecture and you’re not ready to migrate, you can continue using version 2.x until you’re ready to adopt the new architecture.
Update process
Updating to Customer.io Expo plugin version 3.0.0 is straightforward. There are no public API changes.
1. Migrate to the new React Native architecture
If you haven’t migrated to React Native’s new architecture yet, see the React Native documentation for instructions. When your app is successfully running on the new architecture, you can update to Customer.io Expo plugin version 3.0.0.
2. Update the plugin version
Update your package.json to use version 3.0.0 or later:
npm install customerio-expo-plugin@3.0.0
# or
yarn add customerio-expo-plugin@3.0.0
3. Rebuild your app
After updating the plugin, rebuild your app:
# iOS
npx expo prebuild --clean
npx expo run:ios
# Android
npx expo prebuild --clean
npx expo run:android
4. Test your integration
Since there are no public API changes, your existing Customer.io SDK calls will continue to work. However, you should test your app after updating to ensure everything works as expected.
Troubleshooting
If you encounter build errors after updating, perform a clean rebuild:
# Clean and rebuild
npx expo prebuild --clean
npx expo run:ios
npx expo run:android
If issues persist, ensure your app is properly configured for React Native’s new architecture and that all dependencies support it.
Try our MCP server!
Our MCP server includes an integration tool that can help you install and troubleshoot issues with our SDK, including problems with push and in-app notifications. See our MCP server documentation for more information.
