You might have issues delivering your app push notifications for several reasons. You can troubleshoot the delivery issue on different levels:
Panel setup
Check the following steps in your panel setup to ensure your settings are configured correctly.
Add the required credentials to Settings > Mobile App Settings > Push Notification Settings.

Select the application title and time zone on the General tab.

Create the push certificates and upload them to the panel.
The iOS push certificates should not expire. If they are, no push will be delivered.
The iOS Bundle IDs in the Push Certificate should match the package names of the iOS devices, with Development and Production States accordingly. If they don't match, users will not receive push notifications.
You should check the iOS panel server state on Settings > Mobile App Settings > Push Certificates. The application build type and the server state should match. You can see the build type for specific devices in the test device list by the keyword near the Apple logo. Users who downloaded the app from the App Store or Play Store are considered production devices, and the server state of the production panel should be set as production.

If you get the following error when updating the push certificates, you may have missed a step during push certificate creation. Make sure to complete the steps correctly in the p8 and p12 push certificates.

Enable Android Push Messages in the panel, and add the Firebase Cloud Messaging API Key. You can confirm it through Settings > Mobile App Settings > Push Certificates > Android Certificate.

If the app push is not sent on time, set the time zone correctly in Mobile App Settings.

User-level troubleshooting
Follow the steps below to determine whether your user cannot receive app push notifications.
You should add your device as a test device and send a test push notification to your device. After the test push is sent, the system will provide a test push report. You can check this test push report and the respective error on the FAQ about the Test Devices page to understand why you are not receiving the app push.
You should check your user in User Profiles to ensure the push opt-in is true to be reachable on the app push channel and the GDPR opt-in is true. The user must also have an available, valid token.
If you send a test push to your device successfully but not a campaign, you can check your device model. If you have more than one device registered to your user, check which devices the campaign targets in Delivery Devices. Make sure you are receiving the test push on the correct device.
Campaign-level troubleshooting
If a user is receiving push notifications regularly but not certain campaigns, you can check the following settings.
Check Mobile App Settings > Delivery and Conversion > Global Frequency Capping to see whether your push notification is capped due to the message limit.
You can check User Profiles to see whether the user meets the segment criteria in the campaign. You can see the related events and attributes on the user profile. You can also export your mobile app segments to analyze them. If a segment doesn't work, the events and attribute integration may not be set up correctly. In this case, check the test lab to verify the data integration.
Campaign reports
Your campaign reports might show delivered app pushes, but you may not have received them, or there may be no open logs. In this case, your development team should check the push-handling methods if you have more than one integrated vendor (e.g., Firebase or other vendors).
apple-privacy-manifest
Insider One and Firebase count app pushes on different bases, so their numbers are not expected to match. The gap is often larger right after you migrate from Firebase to Insider One. Check the following causes.
Different scope: Firebase reports every push sent through your Firebase project, including pushes from other tools, senders, and app versions. Insider One reports only the pushes sent by its campaigns. To compare, use the same campaign and date range, and look at Delivery Rate and the undelivered reasons in App Push Analytics.
Users who have not opened the updated app: You do not need to migrate push tokens or opt-in status from Firebase. The Insider One SDK collects the push token and the user's push permission from the device when the user opens the app version that includes the SDK. Until then, Insider One cannot reach that user. Reach grows as users update and open your app.
Push permission changed on the device: The change reaches Insider One the next time the user opens the app. Until then, Insider One may still send to a user who turned notifications off, and the push counts as undelivered.
Uninstalled apps: Insider One detects an uninstall after it sends a push. These users appear as undelivered and receive no further pushes.
Another vendor receives the push: If Firebase or another vendor is still integrated in the app, its push handling can interfere with how Insider One pushes are handled. Reports may then show delivered pushes that users do not see, or no opens. Your development team should check the push-handling methods.
Fix provider errors
If many pushes are undelivered, check the error in your reports and the FAQ about Test Devices:
Bad Device Token: The app build and the Push Notification Server State do not match, for example a development build with a production setting. Change the state in Components > Application Settings > Push Notifications, or install the matching build.
Device Token Not For Topic: The certificate topic and the app's Bundle ID do not match.
Mismatch Sender ID: The sender ID and the Firebase API key in the panel do not match the Firebase project the app uses. Update them with the values from your app's Firebase configuration.
Control group on the campaign
If a user receives an app push with empty content in a campaign that includes a control group, your development team should review the push handling methods. This is particularly important if you have integrated more than one vendor (e.g., Firebase or other providers).