SDK integration
This guide assumes that you've already followed the iOS and Android prerequisites.
Batch React-Native Plugin requires react-native 0.77 or higher. If you’re using Expo, version 54 or higher is required.
Batch-React-Native-Plugin is a pure Turbo Module and does not support the legacy architecture anymore since react-native is freezing the legacy architecture codebase. If you are still on the legacy architecture and do not plan to migrate on the new one, please use the Batch-React-Native-Plugin v11.
Integration
Please follow the integration guide according to your application.
Expo IntegrationVanilla IntegrationYour first notification
1. Obtaining Your Device Token on iOS
You can find your device's token using the debug tool or locating the token Batch posts to the Xcode console:
Push token (Apple Push Production): <push token>Based on your Provisioning Profile, the token shown in the console will be Development ("Sandbox/Development") or Production ("Production").
2. Obtaining Your Device Token on Android
You can find your device's token using the debug tool or locating the token Batch posts to the logcat (see here to know more):
Batch.Push: Registration ID/Push Token (FCM): <your device token>3. Sending A Test Push
You can send test notifications to your device with a push token. In the push notification creation form, click the ⚙️ and copy your push token in the corresponding field. Hit "Send a test".
What's next
Congratulations on finishing the integration of Batch Push!
Here are a couple of extra steps you can take before releasing your app:
Small icon / Accent color: On Android, make sure the small icon you are using is opaque white. We also recommend you use an accent color.
Custom user identifier: Add support for custom user identifiers if you are planning to use the Profile API.
Analytics: Add an event dispatcher to automatically track your campaigns in your third-party analytics tool.
Token import: Import your existing tokens if you're coming from another push provider.
Last updated