Expo React Native SDK

​

Release Summary

​

Expo 2.0.1

• Updated the peer dependency on react-native-moengage to ^13.0.0, so the plugin installs alongside react-native-moengage 13.

​

Release Summary

​

Expo 2.0.0

• Expo SDK 58.0.0 or later is required. The Android build toolchain moves to AGP 9.1.1, Gradle 9.3.1, Kotlin 2.3.20, and compile SDK 36. Earlier Expo SDK versions don’t support AGP 9.
• Android: push registration now uses the Firebase Installation ID instead of the FCM token. If you use MoEngage to register for push, move com.google.firebase:firebase-messaging to 25.1.2 or above and complete the Firebase Installation ID integration before upgrading. For more information, refer to Migrating to Firebase Installation ID.
• Android: passFcmPushToken() is deprecated. It continues to work. MoEngage recommends moving to passFirebaseInstallationId().
• Android: the pushTokenGenerated event is deprecated. It continues to work. MoEngage recommends moving to firebaseInstallationIdAvailable, which delivers a MoEFirebaseInstallationIdResult instead of a MoEPushToken.
• Removed support for the React Native old architecture. The plugin now supports only the New Architecture.

• Updated to the MoEngage React Native plugins 13.0.0. Swift Package Manager is not supported for Expo applications, which continue to use the MoEngage Expo config plugin with no change.

​

Release Summary

​

Expo 1.2.0

• The SDK build toolchain now supports the recommended JDK 17. A JDK 19 environment is no longer required to compile the SDK.

​

Release Summary

​

Expo 1.1.1

• Android: Migrated the common Gradle configuration to the Gradle config.

​

Release Summary

​

Expo 1.1.0

• Android: Internal improvements.

​

Release Summary

​

Expo 1.0.1

• Removed the postinstall script to avoid running the tsc command on all projects.

​

Release Summary

​

Expo 1.0.0

• Adding support to integrate the MoEngage React-Native SDK with the Expo framework.