Push

Try it in the demo.

Your app sends push notifications through FCM, Expo or OneSignal with their own SDKs. Point the SDK at SendMock instead and Push shows every notification as a lock screen card, with its data payload, the request and what SendMock answered, in the provider's own shape.

What it solvesCopy Anchor Link

• Seeing the notification without a phone, a Firebase project or an Expo account: the title, body, image and data exactly as your app built them.
• Automated tests: wait for "the push to this device" and assert on its title or data, instead of mocking the SDK.
• The answers your code handles: FCM's message name, Expo's tickets and receipts, OneSignal's notification id, all in the provider's format.

How it connectsCopy Anchor Link

Use itCopy Anchor Link

1. Point your SDK at SendMock:

   • Expo: set the environment variable before your server starts.

     Copy Text

     EXPO_BASE_URL=http://127.0.0.1:8026

   • OneSignal (Node): give the client SendMock as its server.

     Copy Text

     const configuration = OneSignal.createConfiguration({
       restApiKey: "any",
       baseServer: new OneSignal.ServerConfiguration("http://127.0.0.1:8026", {}),
     });

   • FCM: send to http://127.0.0.1:8026/v1/projects/<your-project>/messages:send; firebase-admin has no base URL option, so route its requests to that address in development.

2. Send a notification from your app (an order shipped, a chat message). A row appears with its title, device token, provider and status.
3. Click the row. The drawer shows the lock screen card (switch between iOS and Android), the data payload, the request and the answer.

Test failures with magic tokensCopy Anchor Link

A device token (or Expo push token, OneSignal subscription or alias id) that contains one of these words fails the way the provider fails, so you can test how your app handles a dead or bad token. The notification is still listed, as Failed, with the reason and the error your app got.

When every OneSignal recipient is refused, the answer is { "id": "", "errors": ["All included players are not subscribed"] }, as OneSignal answers it.

Everything on this screenCopy Anchor Link

• Filters: a chip per provider (All, FCM, Expo, OneSignal), Sent and Failed, and a device token filter (exact match).
• The table: the notification's title (or its body when it has none), the device token, the provider, the status and the time. FCM topic and condition sends show as topic:<name> and condition:<expression>, OneSignal aliases as <label>:<id> and segment sends as segment:<names>.
• Clear all: deletes every notification the filters show, after asking.

The notification drawerCopy Anchor Link

Click a row (or open ?push=<id>; Esc closes): the phone preview in the style of the message's platform (iOS puts the image beside the text, Android below it), the status and the reason when it failed, the provider, the device token, the provider's message id, the project and the time, the Data payload as key and value rows, the Request and the Answer as JSON with copy buttons, and Delete.

Every control and text, one by one: Push in depth.

CustomizeCopy Anchor Link

• Projects: send with X-SendMock-Project: <key>, or put /projects/<key>/ before the provider's path in the base URL, to keep each app's notifications apart (Projects).
• One address per provider: without the provider port, use http://127.0.0.1:8025/providers/fcm, /providers/expo or /providers/onesignal as the base URL.

From the CLI, API and AICopy Anchor Link