You are here:   Table of contents / Marketing / Push Notifications

Push Notifications - Troubleshooting | Android

If you notice that a push was not sent out, start by checking the push history list
You can find it in the menu Marketing > Notifications  > Push  History . 

If the status is green, this means that the push was sent to your users properly.

If you have an error:
1. Check all the followings points in this online help, for the platform impacted.
2. Contact the support team specifying in details if some of your settings needs to be updated in your back office.


1

Status shows a green badge but the push wasn't received

Remember to check that notifications are authorized on your device :

- On iOS, in your phone settings
- On Android, in the settings page of the application (if you have included this page in your application)

Even if there is no Error notice it is possible that a push showing a green badge was not sent out to recipients.

We must remind you that GoodBarber doesn't handle the distribution of push notifications to recipients, but only sends on the dispatch request to Apple and Google servers. The request is then put on hold on their servers while waiting for dispatch to the recipients


2

Android - Google Cloud Console settings

In the history, your push shows an orange badge and the mention "Push sent out on iOS and with error for Android".
This means, either that there is an error with your project number or your Firebase project's settings.

1. Log in to your Google console
2. Select your project
3. Check on your dashboard Google if your project ID matches the Google Console project ID in your back office (Menu Sales Channels > Android App  > Certificates).

(There can be an API display error on browsers other than Chrome, we therefore recommend that you use this browser for this check up).

picture

3

Android - Firebase Sender ID

1. Login to Firebase console
2. Check that your project Firebase is linked to your Google Console Project:
- Select your firebase project (created when building your Android app for the first time at step 7 of this online help )
- Click on the icon to the right of "Project Overview"
- Choose "Project Settings"
- Click the tab "Cloud Messaging"
- Check if the Sender ID on firebase matches the Google Console project number  in your back office (Sales Channels > Android App > Certificates ). 

picture

4

Android - Firebase Server Key Token

1. Login to Firebase console
2. Select your Firebase project (created when building your Android app for the first time at step 7 of this online help )
3. Click on the icon to the right of "Project Overview"
4. Choose "Project Settings"
5. Click the tab "Cloud Messaging"
6. Check if the Server key token on Firebase matches the Firebase token for Cloud Messaging in your back office (Sales Channels > Android App > Certificates ). 

picture

5

Android - Firebase Android App

1. Login to Firebase console
2. Select your Firebase project (created when building your Android app for the first time at step 7 of this online help )
3. Click on the icon to the right of "Project Overview"
4. Choose "Project Settings"
5. Click the tab "General"
6. Check if the Package nameset on Firebase matches the Package name in your back office (Sales Channels > Android App > Certificates ).  

picture

Once you have checked the points 2 through 5 above, contact the support team  specifying in details the following elements:
1. Which one of your settings need to be updated in your back office:
- Google console project ID
and/or
- Firebase Sender ID
and/or
- Server key
2. If the package name is properly set on your Firebase console.

Depending on your configuration, the support team will give you with instructions on how to fix it.

Note: Once the issue is resolved, you will have to regenerate the Android application and send an update to the store, if it was already published.