Push Notifications aren't delivered. What could be the cause?¶
To check, please follow the below flowchart. This can also be applied for situations when push API could not be delivered.
1.Launch the app and upload session data¶
Once you open the app, session information is uploaded periodically.
2.Set the device as audience¶
Please create an audience that includes the users on device.
If you cannot find users¶
Click here for Can’t find user?. Unless the session data is not uploaded to Repro’s system, you will not be able to send push notifications.
3.deliver push notification to an audience¶
Create a new push notification and set the delivery condition to audience.
If the delivery was successful¶
It is possible that the delivery conditions weren’t included in the specified device. Please check that the device adheres to the delivery conditions.
How to check:
Event, event property: I don't see any events being uploaded. What could be the cause?
User profile: How to check if a User Profile is registered.
If you were able to receive audience but not the push API, please check the below.
Unsuccessful request for push API
Targeted User ID isn’t included in the request payload for push API.
[Android] For CustomJSON , the receiver was not implemented incorrectly, or not at all.
If the push notification delivery was unsuccessful¶
Please follow the below steps.
Warning
Please don’t start the app until you have checked the following audience steps. There is a possibility that correct judgements will not be made due to the change in condition from uploading the session information to Repro.
4.Check the different audience categories¶
Please refer to the User Information for device verification under audience.
If Push Tokens don’t exist¶
Please check to see if there are any problems with acquiring Push Tokens.
If Push Token Availability was denied¶
It is possible that the push notification certificate is incorrect. Please check the below settings under SETTING > PUSH NOTIFICATION SETTING.
[iOS] The certificate is for development, but using the production app installed from the app store to verify
[iOS] The certificate is for the production, but using the developmental app built from the app development environment to verify.
[iOS] The name of the certificate (Bundle ID) doesn’t match with the app’s Bundle ID.
[Android] The registered FCM Server Key doesn’t correspond with the google-services.json within the app.
Note
The iOS certificate will be displayed as follows under Platform through SETTING > PUSH NOTIFICATION SETTING.
Production certificate : APNS
Development certificate : APNS_SANDBOX
If the Push Permission is denied¶
Turn on the push notification permission from your settings.
If none of the above apply¶
Push notifications will not be displayed if one of the below applies.
[iOS] The certificate set in the SETTING > PUSH NOTIFICATION SETTING screen has expired.
[Android] For Androids over 8.0, "the notification channel has not been set.
[Android] The push display Receiver for Repro isn’t registered
[Android] For CustomJSON , the receiver was not implemented incorrectly, or not at all.
Due to signal, power, and network conditions of the device, there is a possibility that push notifications are not able to be received.