Testing Expo push notifications in development builds without production APNs/FCM credentials

Answer

Yes. You can verify remote push delivery in a development build using Expo’s own push notification service; you do not need to upload your own APNs keys or FCM server keys.

Confirmed facts

• Expo maintains its own APNs key and FCM server key tied to your Expo account. When you call expo push:send or POST to https://exp.host/--/api/v2/push/send, Expo forwards the message to the appropriate service using those credentials.
• The push token you obtain with Notifications.getExpoPushTokenAsync() is valid for the Expo push service regardless of whether the app is a development build, Expo Go, or a production build—provided the token matches the build type.
• On Android, notification channels must be created inside the app (e.g., via new NotificationChannel(...)); Expo’s service does not create them, but it forwards any channelId you set to FCM unchanged.
• On iOS, the payload is forwarded to APNs exactly as Expo receives it; you can set badge, sound, contentAvailable, etc., and they will be applied.

Likely explanation

Expo’s push service acts as a thin relay: it receives your JSON payload, adds the device‑specific token, and sends it to APNs/FCM using Expo’s own keys. Because the relay does not modify the alert title/body or most options, the behavior you see in a dev build mirrors what you would see in production, except for Android notification channels, which you must configure in the app itself.

Steps to test in a development build

1. Install the notifications plugin (if not already):

   expo install expo-notifications

2. Request permission and retrieve the Expo push token (run this once per device/install):

   import * as Notifications from 'expo-notifications';
   
   async function registerForPush() {
     const { status } = await Notifications.requestPermissionsAsync();
     if (status !== 'granted') {
       alert('Permission not granted');
       return;
     }
     const token = await Notifications.getExpoPushTokenAsync();
     console.log('Expo push token:', token.data);
     // Send this token to your server or copy it for manual testing
   }
   

3. Make sure Android notification channels exist (example code, run once on app start):

   import { Platform } from 'react-native';
   import * as Notifications from 'expo-notifications';
   
   if (Platform.OS === 'android') {
     Notifications.setNotificationChannelAsync('default', {
       name: 'default',
       importance: Notifications.AndroidImportance.MAX,
     });
   }
   

4. Send a test notification via Expo CLI (replace EXPO_PUSH_TOKEN with the token from step 2):

   expo push:send --token EXPO_PUSH_TOKEN --title "Test" --body "Hello from Expo"

   Or via curl:

   curl -H "Content-Type: application/json" \
     -X POST https://exp.host/--/api/v2/push/send \
     -d '{
       "to": "EXPO_PUSH_TOKEN",
       "sound": "default",
       "title": "Test",
       "body": "Hello from Expo",
       "data": { "extra": "value" }
     }'
   

5. Verify receipt:

   • Check the device’s notification tray – you should see the test message.
   • In the app, add a listener to confirm foreground handling:

   const notificationListener = Notifications.addNotificationReceivedListener((notification) => {
     console.log('Received:', notification);
   });
   

6. Inspect the API response – a successful send returns:

   { "data": { "status": "ok", "receipts": [ { "messageId": "...", "status": "ok" } ] } }
   

SDK version considerations

• Expo SDK 44 (or newer) paired with expo-notifications ≥ 0.16 provides reliable token retrieval and background handling in both development builds and Expo Go.
• Older SDKs (< 44) may miss the token on Android when the app is backgrounded; upgrade if you encounter silent failures.
• For iOS, a physical device is required for remote push testing; simulators cannot receive APNs pushes.

Missing diagnostic detail

Do you have a physical iOS device available for testing? If you are only using a simulator, iOS remote push tests will not work regardless of the steps above.