9

Lets say I have Google Cloud Project (GCP1) with GCM turned on with Client id P1.

Now I have created a standalone Firebase project F2 WITHOUT importing it to GCP1. I have also released F2 to production. (Alternatively, I have imported F2 from an existing firebase.com project into the new Firebase console).

I use a backend server to send push notifications. When I send a push to a GCM token generated via GCP1 from the F2 project, it fails (naturally) because of incorrect client ID. Are there work-arounds to enable use of GCM tokens generated for P1 within F2?

Arun Venkatesan
  • 403
  • 3
  • 7

1 Answers1

14

When sending messages from your back-end server, you need to authenticate the request with the API-KEY associated with project (sender-id) used to generate the GCM/FCM token.
Due to security restrictions here are no workaround for this.

For existing GCM users the best migration consists in importing the old project into the Firebase Console. This will allow you to target both old and new client, since the sender-id will not change
Steps here: https://developers.google.com/cloud-messaging/android/android-migrate-fcm

If that is not option (you have already created a new Firebase Project distinct from the previous Google Cloud Project) you have two possibilities:

  1. Easier and recommended approach: change your back-end to store which client originated the gcm/fcm token. Then use the correct API-KEY when sending messages from your back-end. (the API-KEY associated to the old project for old clients, and the new API-KEY for new clients that are using the new Firebase project).

  2. If you cannot change your back-end at all: in FCM you can create an additional token for the old SenderID, using the API:
    FirebaseInstanceId.getInstance().getToken("old-sender-id", "FCM")
    Because this token is associated to the old-sender-id your back-end will be able to send messages to it using the API-KEY of the old project.
    Note: this doesn't affect the Firebase Console which is based on the new-sender-id.
    That console will be able to target only the new clients that are including the firebase sdk and the associated google_services.json file.

Diego Giorgini
  • 12,489
  • 1
  • 47
  • 50
  • 1
    Thanks for the information. I'm trying to solve a similar situation. I already have an APP with many users registered under a GCM project. Since a few months ago we also have a new version that uses a Firebase project. The Firebase project and GCM are not the same. Now that I want to upgrade GCM to FCM I find myself in trouble as I can't have the two projects linked together. I still need to be able to send messages to old users and new users, I don't mind not using the Firebase console, I just want to be able to target everyone. Any ideas? Is option 2 the solution? – Roberto Jul 28 '16 at 14:31