Test Push Troubleshooting¶
Once you’ve integrated the Flurry SDK with push and uploaded your push credentials in Admin>Apps (on the Flurry dashboard), the next step is to send yourself a test push.
You can send a test push by going to the Marketing section of Flurry, selecting the app you want to test and clicking the “Create Push Campaign” button. Continue through the campaign set up until you get to the “Review Your Campaign” page.
There is a text field below “Preview Campaign”
- For iOS, enter your IDFA or IDFV.
- For Android, enter your Google Advertising ID
- If your push will be sent in multiple languages, use the “Preview” language toggle to select the language you’d like to preview.
- Click the “Send” button
If you see a green success message, great! Look for the test push notification on the device you selected. When your push arrives, review the display and click on it to open to confirm this works correctly. If you included a deep link, make sure the deep link is opened when you click on the notification. (If you have deep link errors, please review the Flurry onboarding documentation to verify your deep link implementation conforms to Flurry’s guidance.) Note: If you successfully send a test push through test push functionality but don’t receive a message from a campaign, doublecheck the Flurry API key of the app you are testing against the Flurry API key of the app ypou selected for the campaign.
If you see an error message, look for the error key in the red error message. Then use the tables below to determine the steps to resolve.
Below you may find errors of the following types:
- Cross-platforms errors - These errors indicate a platform-agnostic issue
- Android errors - These are Firebase errors we received from FCM
- iOS errors - These are APNs errors we received from Apple
|Invalid value||Flurry recommendation|
|NoValidPushCredential||Verify that you have uploaded valid Push Credentials in Admin>Apps.|
|TokenFetchFailure||This may be a temporary issue. Please wait a few minutes and try again. If problem persists, please contact firstname.lastname@example.org for assistance.|
|NoDevicePushToken||We don’t have a push token for this device. Please open the app and try again. If problem persists, please contact email@example.com for assistance.|
|UnrecognizedDeviceId||We weren’t able to find a push token because the device identifier you provided isn’t recognized. Please double check the identifier provided. You must enter an IDFV/IDFA (iOS), Adverting ID/Android ID (Android) or push token. Contact firstname.lastname@example.org for assistance.|
|NoDeviceDataForProject||Flurry is unable to send a Test push to this device ID because the IDFA/advertising ID you entered isn’t associated with the push token that Flurry has for your device. If feasible, try a Campaign push or use a push token to send a test push. On iOS, you can also use the IDFV for your project. If you require assistance, contact email@example.com.|
|PayloadTooBig||The push notification you specified is too big to send. Please return to the “Build Your Message” step and reduce the text/emojis in the Title or Body, or try cutting down the key-value pairs specified.|
|Other errors||Please contact firstname.lastname@example.org for assistance.|
|Invalid value||Google explanation||Flurry recommendation|
|MismatchSenderId||A registration token is tied to a certain group of senders. When a client app registers for FCM, it must specify which senders are allowed to send messages. You should use one of those sender IDs when sending messages to the client app. If you switch to a different sender, the existing registration tokens won’t work.||
If using auto integration, remove any classes that extend FirebaseInstanceIDService and FirebaseMessagingService. Flurry handles those classes for you.
Also, the Sender ID and API_KEY(Firebase API Key) must match. Select your project in the Firebase console and select your project. Find the sender ID in Settings > Cloud Messaging. Double-check that the Firebase API Key belongs to ‘Key for server apps (with IP locking).’
An existing registration token may cease to be valid in a number of scenarios, including:
For all these cases, remove this registration token from the app server and stop using it to send messages.
This indicates that Flurry has your push token but that it is either expired or no longer registered. Make sure the device you are testing with still has the right version of the app installed. In some cases, Google may have refreshed the token so try re-opening the app to make sure Flurry has the most recent token from the device.
Also, doublecheck that the API key of the app you are testing matches the API key of the app selected for the Push Campaign.
|InvalidRegistration||Check the format of the registration token you pass to the server. Make sure it matches the registration token the client app receives from registering with FCM. Do not truncate or add additional characters.||Try logging the token and make sure it matches per Google’s instructions.|
|FCMTemporarilyUnavailable||N/A||Firebase received an error when trying to send the test push to Firebase Cloud Messaging. This may be a temporary issue. Please wait a few minutes and try again. If problem persists, please contact email@example.com for assistance.|
|AuthorizationError||N/A||The app credentials you have provided to Flurry are either out of date or have changed. Please return to Flurry and navigate to Admin > Apps. Find the app you are testing and upload a new Firebase Server Key. Note: Flurry may show that your credential is valid even though it is no longer valid, because the credential may have been refreshed in Firebase after it was uploaded and marked as valid.|
|Any other Android errors||See Google’s support docs.|
|Invalid value||Apple explanation||Flurry recommendation|
|Unregistered||The device token is inactive for the specified topic.||This indicates that Flurry has your push token but there may be an issue with your push certificate. See info on ‘topics’ in APNs Provider Certificate section here.|
|BadDeviceToken||The specified device token was bad. Verify that the request contains a valid token and that the token matches the environment.||
This indicates that Flurry has the device push token but there may be a mismatch between the token environment and the available certs. If you are testing with a Production device, make sure you have provided a valid Production cert. If you are testing in Sandbox, make sure you have uploaded a valid Sandbox cert.
If have installed both production and sandbox version of an app on your device, try uninstalling & reinstalling the version you want to test with, then regenerating a fresh token from that version.
|TopicDisallowed||Pushing to this topic is not allowed.||
With Flurry Push, this issue indicates a bundle ID/cert bundle mismatch. Please confirm that the cert you uploaded to Flurry was generated for the same bundle ID you provide to Flurry.
If confirmed and issue persists, please contact Flurry. This could be related to past updates to your bundle ID.
The app credentials you have provided to Flurry are either out of date or have changed. Please return to Flurry and navigate to Admin > Apps. Find the app you are testing and upload a new Certificate.
Note: Flurry may show that your credential is valid even though it is no longer valid, because the credential may have been refreshed in APNs after it was uploaded and marked as valid.
|Any other iOS errors||See Table 8-6.|