---
title: "Troubleshoot push notification delivery errors"
description: "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 &"
canonical_url: "https://www.goodbarber.com/help/shop/manage-and-send-push-notifications-r54/troubleshoot-push-notification-delivery-errors-a100/"
lang: en
---

# Troubleshoot push notification delivery errors

Source: https://www.goodbarber.com/help/shop/manage-and-send-push-notifications-r54/troubleshoot-push-notification-delivery-errors-a100/

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 following 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, 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**.

## 2. Android - Check if the Google Console and Firebase project match

**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](https://console.cloud.google.com)**
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).*

![](https://cmsphoto.ww-cdn.com/superstatic/1758497/art/default/34456182-31497714.jpg?v=1750107605.792328)

5. Login to [Firebase console](https://console.firebase.google.com/)
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](https://www.goodbarber.com/help/shop/publish-your-android-app-yourself-solo-r62/build-and-test-the-android-ad-hoc-version-a71/) )
- 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)

![](https://cmsphoto.ww-cdn.com/superstatic/1758497/art/default/34456182-31497715.jpg?v=1750107605.804328)

## 3. Android - Firebase Android App

1. Login to [Firebase console](https://console.firebase.google.com/)
2. Select your Firebase project (created when building your Android app for the first time at [step 10 of this online help](https://www.goodbarber.com/help/shop/publish-your-android-app-yourself-solo-r62/build-and-test-the-android-ad-hoc-version-a71/) )
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 name***set on Firebase matches the ***Package name*** in your back office (**Sales Channels > Android App > Certificates** ).

![](https://cmsphoto.ww-cdn.com/superstatic/1758497/art/default/34456182-31497717.jpg?v=1750107605.824328)

## 4. Android - GoodBarber back office

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:

![](https://cmsphoto.ww-cdn.com/superstatic/1758497/art/default/34456182-57293610.jpg?v=1750107605.8403282)

4. Look for the *current_key* value within the *api_key*object of the *google-services.json* (serviceJson) file and check that 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 .**

![](https://cmsphoto.ww-cdn.com/superstatic/1758497/art/default/34456182-63183807.jpg?v=1750107605.852328)

## 5. Android - Google Cloud Console

1. Log in to your **[Google console](https://console.cloud.google.com)**
2. Select your project
3. Go to the menu **API & Services > [Credentials](https://console.cloud.google.com/apis/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.

![](https://cmsphoto.ww-cdn.com/superstatic/1758497/art/default/34456182-57293615.jpg?v=1750107605.8603282)

## 6. Android - Open a support ticket

Once you have checked the points 2 through 5 above, contact the support team specifying in details the following elements:
1. If Google Cloud Console and Firebase **project numbers match**
2. If the***package 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.*