'INVALID_TOKEN' When Sending Push Notifications
Solved
APIs
-
@Joseph-Wiemer No worries - good luck! And keep us posted!
-
Ok guys, I've solved it! It was some godforsaken problem with my .p12 file.
- Tried creating a .p12 file by exporting both the private key and the cert. FAILED.
- Tried creating a .p12 file by exporting just the private key. FAILED.
- Tried creating a .p12 file by exporting just the cert. SUCCESS.
So, notifications are now working for me. Not sure how to mark this question as solved, but it's solved. Thanks for all your help!
-
Awesome - glad to hear it!
I'll mark it resolved for you.
Cheers!
Paul.
-
I just got our iOS Push Notifications working with brainCloud and would like to add a few tips to this thread.
- For the less Mac-Savvy developers like me, here's what it looks like when you only have your certificate with no private key to export as a P12 file:
Notice the selected category is [My Certificates]. Certificates in the [Certificates] category have the P12 export option greyed out.
- I am using Unity as a development platform and for some reason my device would only receive Development Push Notifications even when running in Release in Xcode. It's only after uploading to TestFlight that my Production Push Notifications started working.
