App platform

PushEngage for Expo

Use PushEngage in an Expo app through the PushEngage React Native SDK and an Expo development build. Expo Go is not supported, because it cannot run the SDK's native code.

What you can do with Expo

The same API as bare React Native

Once the development build is in place, the JavaScript API is identical to a bare React Native project.

Full push feature set in a development build

The guide lists deep linking, segments and attributes, goal tracking, and trigger campaigns as supported, plus rich notifications once you add a Notification Service Extension.

Expo tooling keeps working

After prebuild you can still use EAS Build and over-the-air updates with EAS Update.

Example config plugin for regenerated projects

If your native folders are regenerated on every build, the guide includes a local Expo config plugin you can copy to reapply the App Group key and Android notification permission.

Path from expo-notifications

The guide walks through replacing Expo's built-in push service: swap the permission request and tap handlers, and send through the PushEngage REST API.

How to set it up

  1. Install expo-dev-client and the @pushengage/pushengage-react-native package.
  2. Run npx expo prebuild –clean to generate the ios and android folders.
  3. For iOS, open the generated workspace in Xcode, add Push Notifications, Background Modes with Remote notifications, and App Groups, then add PushEngage_App_Group_Key to Info.plist.
  4. For Android, add the JitPack repository and the Google Services plugin, place google-services.json in android/app, and add the POST_NOTIFICATIONS permission to the manifest.
  5. Build a development client with npx expo run:ios or npx expo run:android, or with an EAS Build development profile.
  6. Initialize the SDK with your App ID in index.js before the app is registered, then request notification permission in your app.
  7. Create your production build with EAS Build.

Full guide: PushEngage with Expo and bare workflow

Good to know

  • App push and the React Native SDK are listed on every PushEngage plan, including the free plan. Goal tracking, custom triggered campaigns, and in-app messages need a paid plan.
  • The guide lists Expo SDK 49 or later, the EAS CLI, an Apple Developer account for iOS, and a Firebase project for Android as prerequisites.
  • Expo Go cannot run PushEngage. Test with a development build on a physical device, since simulators do not receive push notifications.
  • Prebuild regenerates the native folders from scratch. Commit the ios and android folders, or use a config plugin, so your PushEngage setup is not lost.
  • The Push Notifications and Background Modes capabilities need entitlements, so a config plugin alone cannot set them. The guide suggests configuring them once in Xcode.
  • PushEngage does not publish its own Expo config plugin. The one in the guide is an example to copy into your project.

About this connection

  • Expo support comes through the PushEngage React Native SDK, which PushEngage builds and maintains. It is not a partnership with Expo.
  • There is no separate Expo package. You install @pushengage/pushengage-react-native from npm.
  • PushEngage's API docs list Expo development builds as supported with manual native configuration, bare React Native as the recommended setup, and Expo Go as not supported.
  • The SDK source is public on GitHub in the awesomemotive/pushengage-react-native repository under the MIT license.

PushEngage Partner Directory

Ready to add push to your Expo app? Start with the setup guide.

PushEngage has a free plan, so you can install it and send your first campaign before you pay anything.