All posts

Test push notifications before launch: a checklist

· 7 min read

Push notifications are easy to ship and easy to get wrong. When they fail, nothing crashes. The prompt never shows, the token is wrong, or the message goes to the wrong server, and you just see nothing. This post is a short way to test them before launch: the permission prompt, a first test message, the iOS environment trap, and what an outside tester should check. I checked the vendor pages below in November 2026. They change, so check them again before you rely on a detail.

Why push needs its own test

You usually test push on your own phone. On that phone you said "Allow" months ago, so you never see the prompt a new user sees. Your token is old and works. Your build is a development build. A stranger has none of that.

Short answer: test the prompt on a fresh install, send a real message to a real device, make sure your server uses the right Apple environment, and ask someone else to try it on their phone.

The permission prompt

iOS

Apple's page on asking permission to use notifications says "To ask for authorization, get the shared UNUserNotificationCenter instance and call its requestAuthorization(options:completionHandler:) method." It also says "The first time your app makes this authorization request, the system prompts the person to grant or deny the request and records that response. Subsequent authorization requests don’t prompt the person."

Apple's Human Interface Guidelines say "You need to get permission before sending any notification. The system lets people change this decision in settings". For promotional or marketing notifications they ask for more: "Before you send these notifications to people, you must receive their explicit permission to do so", with an interface that "gives people a clear way to opt in or out". They add that "you must also provide an in-app settings screen that lets people change their choice." So test both places: the phone's settings and your own.

The asking-permission page also covers provisional authorization: "Use provisional authorization to send notifications on a trial basis." It says the system delivers these quietly: "they don’t interrupt the person with a sound or banner, or appear on the lock screen. Instead, they only appear in the notification center’s history."

Android

Android's notification runtime permission page says "Android 13 (API level 33) and higher supports a runtime permission for sending non-exempt (including Foreground Services (FGS)) notifications from an app: POST_NOTIFICATIONS." Older versions are not covered on that page, so test an older phone yourself if you support one.

The page says "If a user installs your app on a device that runs Android 13 or higher, your app's notifications are off by default." If the user taps "don't allow", "your app can't send notifications unless it qualifies for an exemption." Its best-practice advice is "Before you ask users to grant any permissions, let them familiarize themselves with your app." For apps that target Android 13 or higher, it says "your app has complete control over when the permission dialog is displayed." Its examples of a good moment include "The user taps an "alert bell" button."

For permission timing in general, see testing the first 60 seconds of your app.

Send a test message

Firebase Cloud Messaging has a built-in way to send a test message to one device. On Android, the Firebase page for your first message says "On initial startup of your app, the FCM SDK generates a registration token for the client app instance." The steps are to make sure the app is in the background on the device, select "Send test message", and enter the token in the field labeled "Add an FCM registration token".

The iOS version of that page is similar. It says "By default, the FCM SDK generates a registration token for the client app instance on app launch." You select Test and enter the token in the field labeled "Add a Firebase Installation ID or FCM registration token". It says "the targeted client device, with the app in the background, should receive the notification."

On devices, the Android page says "FCM clients require devices running Android 7.0 or higher that also have the Google Play Store app installed, or an emulator running Android 7.0 with Google APIs." The iOS page does not mention simulators, so I won't say anything about them. A real phone is the safe test.

iOS: development vs production

This is the classic bug. Apple's page on sending notification requests to APNs lists two servers: "Development server: https://api.sandbox.push.apple.com:443" and "Production server: https://api.push.apple.com:443". It says "Use the production server for your shipping apps and the development server for testing."

Which one your build uses depends on how it was signed. The aps-environment entitlement page says "if you're using a development provisioning profile, Xcode sets the value to development. Production provisioning profile and Prerelease Versions and Beta Testers use production." It adds "The development environment is also referred to as the sandbox environment." TestFlight is Apple's beta tool, so I read "Beta Testers" as covering TestFlight builds, but the page does not use the word TestFlight. Check your own build.

So the bug looks like this. Your server sends to the sandbox server, which works on your Xcode build. A TestFlight build gets a token for the other environment, and nothing arrives. The fix is to make the environment a setting you can see and change on your server, not a constant. For how to get a build to outside testers, see TestFlight external testers and public links. For Android builds, see Firebase App Distribution.

Web push, in one paragraph

If your web app also asks for notifications, MDN's page on Notification.requestPermission() says "the request should be made in response to user interaction". So ask after a tap, not on page load. For sharing a web build with testers, see how to share a web app link.

What testers should check

A tester has no old permission answer and no old token. That makes them the best person to check the parts you cannot see. Here is what I would ask for:

  • The prompt. Does it appear at a sensible moment, and do you understand why the app asks?
  • Denying. If you tap "don't allow", does the app still work, and does it say how to turn notifications on later?
  • Three states. Does a test notification arrive with the app open, in the background and fully closed?
  • The tap. Does tapping it open the right screen?
  • The lock screen. Is the text readable, and is it cut off?
  • Duplicates. Did one message show up twice?
  • Turning it off. Does switching notifications off, in the phone settings or in the app, really stop them?

Here is a task text you can paste and change:

"Install the app on your phone and open it. Tell me when the notification prompt appears and what you thought it meant. Tap Allow. I will send you a test notification: tell me whether it arrived with the app open, then with the app in the background, then with the app closed, and what happened when you tapped it. Then turn notifications off and tell me if one still came. Please tell me your phone model and OS version."

For the general method, see how to write a test task. You need a way to send the tester a message, so give them a button in a test screen, or tell them when you will send it.

Where TestSwap fits

TestSwap is a free site where app makers review each other's apps. It is not affiliated with Apple or Google.

  • Makers post web, iOS and Android apps with a link testers can open or install, like a TestFlight link or a Google Play testing link.
  • You can add a test login that only signed-in testers see.
  • Everyone starts with 3 credits. Writing a review earns 1, and each review your app receives costs 1.
  • The maker can rate each review 👍 or 👎, and a 👎 takes back the reviewer's credit.

Testers on other phones and OS versions can tell you whether the prompt and the notifications behaved. I can't promise how many testers or reviews you will get.

The push notification checklist

  1. Test the prompt on a fresh install, not on a phone that already said yes.
  2. Ask at a moment that makes sense, and say why before the system prompt.
  3. Check that denying the prompt does not break the app.
  4. Make sure you can find the device token, and that your server can store a new one.
  5. Send a test message to a real device from the Firebase console.
  6. On iOS, check that your server sends to the same environment as your build.
  7. Test arrival with the app open, in the background and closed.
  8. Tap the notification and check that it opens the right screen.
  9. Read the text on a lock screen.
  10. Check for duplicates.
  11. Turn notifications off, in the phone settings and in your app, and check that they stop.
  12. Give a tester a short task and ask for their phone model and OS version.

Try it

Do the fresh-install test on your own phone today. Then post your app on TestSwap with a task like the one above, and review someone else's app first to see how it works. Tell me what's missing or broken (@dizid on X).