Push Notifications - Troubleshooting | Native apps

If you notice that a push was not sent out, start by checking the push history list. 
You can find it under the menu Notification > 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 following points in this online help, for the platform impacted.
2. Contact the support team , specifying in detail if some of your settings need to be updated in your back office.

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, a push showing a green badge may not have been sent 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. 

In the history, your push shows an orange badge and the mention "Push sent out on iOS and with error for Android".
This means there is an error with either 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 what is your project ID
It should match the Google Console project ID in your back office (Publish > Android > Certificates ).

4. Check what is your Project number, you'll need it in the next steps

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

5. Login to Firebase console
6. 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 10 of this online help )
- Click on the icon to the right of "Project Overview"
- Select "Project Settings"
- Click the tab "Cloud Messaging"
- Check if the Sender ID on Firebase matches the Google Cloud Console Project number (see step 4 above)

1. Login to Firebase console
2. Select your Firebase project (created when building your Android app for the first time at step 10 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 (Publish > Android > Certificates ).

1. Go to the menu Publish > Android App > Certificates
2. Download both the serviceJson file and Service Account file
3. Compare both files and check if the project ID is the same, these IDs must match for the push notification service to locate your app:

4. Look for the current_key value within the api_key object of the google-services.json (serviceJson) file and check this API key is the same as the Google API key for the Android apps declared in your back office under the menu Publish > Android App > Certificates .

1. Log in to your Google Cloud console
2. Select your project
3. Go to the menu API & Services > Credentials
4. Locate the API key declared in the google-services.json file at step 4.4 above.
5. To fix push notification errors, you must select the Restrict key option.
Ensure the following 2 APIs are added to the list of restrictions:
- Maps SDK for Android 
- Firebase Installations API 
6. Save your modifications.

Once you have checked the points 2 through 5 above, contact the support team  specifying in detail the following elements:
1. If Google Cloud Console and Firebase projects number match
2. If thepackage name is properly set on your Firebase console
3. If the project_id differs on your google-services.json file and Service Account file
4. If the API key declared in the google-services.json file is restricted properly

Depending on your configuration, the support team will give you 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.

In the case of an error with the iOS push, always check the validity of your certificates in the menu Publish > iOS > Certificates in your backend.

- If the certificate is expired, read the online help regarding the update of your iOS certificates and continue with the process as described.
- If the dispatch error on iOS remains with the updated certificates, please read on.

1. Log in your Apple developer account >Certificates, Identifiers & profiles https://developer.apple.com/account/resources/certificates/list
2. In the Identifier menu, select the App ID registered in your backend in Publish > Certificates > iOS
3. Click on the App ID to display the capabilities.
4. Scroll down until you find the line "Push Notifications". 
4. Click on Configure or Edit 
 

The Push Certificate must be a Production SSL Certificate.

If you created a Development SSL Certificate instead, the push won't work.

To fix this:

1. Click on the Revoke button to delete the existing certificates
2. Click on done at the bottom of page.
3. Follow the online help regarding the update of iOS certificates, starting at step 4.