Firebase console is broken, and senderID, all server keys are changed

I created the Firebase application, created all the senderIDs and server key for Cloud Messaging. I tested and everything worked. That was last week.

This week I do more testing and get the error returned to my php script: { ["error"]=> string(13) "NotRegistered" }

I sign up back to Firebase, go to "Project Settings" - "Cloud Messages" and look at the BOTH server key and change the sender ID. In addition, the iOS-related section of the application simply rotates and rotates and never loads this section. I did not do anything. Is anyone else experiencing this? How can i fix this? I don’t even see the full server key ... and when I tried to associate the new senderID with my Play Store Developer application console, it made a mistake indicating "invalid senderID". Thus, I don’t even think that the new senderID and server keys will work ... but at the same time, the ones I used do not work either.

0
firebase-cloud-messaging google-developers-console
Jun 24 '17 at 22:10
source share

No one has answered this question yet.

See similar questions:

6
Firebase dashboard cannot see the full server key

or similar:

124
Where can I find the API for Firebase Cloud Messaging?
25
Firebase Cloud Messaging from Java instead of Firebase Console
10
Firebase API Key Constraint
2
How to check if a notification key exists in a CloudBase Firebase server?
0
Firebase Cloud Messaging No Server Key
0
New Firebase Cloud Messaging Server Key Continues to Change Every Week
0
Is the new Firebase messaging server server limited for messaging?
0
Will the effect of changing the sender / server code of Firebase currently signed topics?
0
Update firebase key name in developer console
0
Clusters with multiple CloudBase Firebase servers



All Articles