This repository has been archived by the owner on Dec 1, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 511
Uploading new p12 for GCM #250
Comments
i have same problem T^T |
I stuck with the same issue. Is any other alternatives ? |
Same here. |
I was able to get this working by signing up for firebase and making the changes there. I did not change any of my code (except the newly generated key) and still use the old GCM url, but it works. |
While that is an option, it is not one that the OP wants to use. |
@Moghul I'm OP so......... yeah... :D |
Oh. I should have paid a bit more attention. Glad you found a workaround :) |
I contacted Google about this issue: They are aware of it, working on it, but don't have any timeline for when it will be fixed. They suggest the workaround via Firebase. I have compiled here the steps to update the certificate via Firebase:
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
My certs have expired and I've regenerated them. Now I'm going to upload the new .p12 files and I see the page has what appears to be an angular error so I can't upload them.
As a note, I do NOT want to switch to firebase.
url: https://developers.google.com/mobile/add?platform=ios
The text was updated successfully, but these errors were encountered: