Get your app ready for push delivery
Understand the Apple, Firebase, and device requirements without exposing credentials.
Last updated 9 September 2026
On this page
Ask your developer for the right configuration
Push credentials belong to the app that receives notifications. Open the app’s push setup in App settings. Your developer or the person managing your Apple and Firebase accounts should prepare the credentials for that exact application.
For iOS
The Apple setup uses an APNs authentication key together with its Key ID, Team ID, bundle identifier, and environment. Development builds and production builds can use different APNs environments. The device token and the signed build must match the environment used for delivery.
For Android
The Firebase setup uses the app’s Firebase project and service-account configuration. Make sure the project matches the one used by the Android build. A valid-looking file from a different project will not establish a working delivery path.
Verify the complete chain
Save the app’s credentials in UserGist’s dedicated settings, not in an article, screenshot, or campaign body.
Open the app on a physical test device and grant notification permission.
Confirm the device registered with UserGist under the expected app and identity.
Send a test and confirm it on the device, then inspect any delivery error if it does not arrive.
When a test fails
Check the credential metadata, app identifiers, environment, token freshness, and device permission. Provider acceptance and physical display are separate checks. Use the platform developer guide for the exact Apple or Firebase setup steps.
Related guides
Prepare and test a native push notification