If you are having trouble integrating the SDK, uploading your certificates or sending notifications, here are some suggestions.
Batch is published to Maven Central. Sometimes, jCenter does not correctly mirror it, breaking the auto update of the artifacts.
To fix this, either switch to an explicit version (such as
1.12.0 rather than
1.12+), or add
mavenCentral() to your repositories in your build.gradle.
Please ensure you added the Play Services library in the dependencies. If you use Proguard (
"minifyEnabled=true" in the Gradle build), make sure you have added Batch's Proguard rules.
If you use Proguard, please make sure you have added Batch's Proguard rules. If your integration worked on the debug builds, it is probably because Proguard was disabled on that configuration.
This usually happens when the SDK is not integrated in ALL your activities.
Please make sure you call
Batch.User methods after
Batch.onStart() and before
There are several points you should check if Batch is unable to find a start event for your app:
If Batch is unable to find a token, here are some suggestions to find the issue:
Here are several points that may help:
You can also check the status of every message sent to a specific device token (received, device disconnected, etc) using the FCM Diagnostics from the Google Play Developer Console.
There are several points you should check if Batch doesn't show any data on your dashboard:
GCM tokens are linked to a single Sender ID. Make sure the GCM Server API Key used in Batch's dashboard (⚙️ Settings → Push settings) matches the GCM sender ID used in your app. You will find more information here.
This error happens when GCM is not available for a short period of time. Try again later or fallback on cellular network.
Please reach us at firstname.lastname@example.org. Our team will help you to fix the issue.
You can find the list of GCM and Batch internal errors in the Notifications tab, by hovering on the error count.
GCM/FCM refused the credentials supplied in your app configuration
GCM sends this error when the token Batch tries to push is not valid anymore. This usually happens when users uninstall/reinstall your app.
On Android, tokens are linked to a specific sender ID. GCM will systematically send this error when a token is pushed with the wrong sender ID. Make sure you are using the same Sender ID you were using with your old push provider.
This internal error happens when the number of maximum send attempts is reached for a token. Feel free to reach us if you are seeing to many max_retry_attemps errors.
If the number of max_retry_attempts error suddenly increases, make sure you are using a "Server API key" to communicate with GCM (Developer dashboard → Credentials → API keys). If you are using an Android API key, you should generate a new Server API key and paste it in Batch's dashboard (⚙️ Settings → Push settings).