SOLVED 'INVALID_TOKEN' When Sending Push Notifications


  • brainCloud

    And note, if you change the entitlement, after rebuilding, you'll need to re-run the app on your device - which I believe will cause it to register a new, updated device token... You'll want to use that one for your tests...

    Do I have that right Steve?



  • Ok guys, I've solved it! It was some godforsaken problem with my .p12 file.

    1. Tried creating a .p12 file by exporting both the private key and the cert. FAILED.
    2. Tried creating a .p12 file by exporting just the private key. FAILED.
    3. 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!


  • brainCloud

    Correct! @Paul-Winterhalder Keep us updated @Joseph-Wiemer



  • @Paul-Winterhalder

    #1 - My app was not running at the time, and I tried again.
    #2 - That's correct. And I'm still getting the same INVALID_TOKEN error in "Recent Errors".

    My app does have the correct "production" entitlement, yes.



  • @Steve-Jones Yes to both. My cert is for distribution and my app entitlement is set to "production". No, the notification from pushtry.com never appeared on my device, despite the service claiming to have been successful.


  • brainCloud

    Dumb question - do you have any other devices that you can load your app on and try with? It's certainly suspicious that pushtry isn't working for you.

    At this point I'd be removing the app from the device, re-installing, re-running (to register what I believe would be a new device token), and retrying the send - both from pushtry and brainCloud.

    If both pushtry and brainCloud don't work - the common denominators are your app's configuration, the device itself, and Apple's servers...



  • @Paul-Winterhalder Yes, I do have other devices I could try. I realize this probably isn't a brainCloud problem, so I appreciate all the help you guys have given me, here. Thank you, and I'll keep trying to figure it out.


  • brainCloud

    @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.

    1. Tried creating a .p12 file by exporting both the private key and the cert. FAILED.
    2. Tried creating a .p12 file by exporting just the private key. FAILED.
    3. 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!


  • brainCloud

    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.

    1. 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:

    Screen Shot 2019-06-19 at 4.02.20 PM.png

    Notice the selected category is [My Certificates]. Certificates in the [Certificates] category have the P12 export option greyed out.

    1. 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.

Log in to reply