<![CDATA['INVALID_TOKEN' When Sending Push Notifications]]>I'm getting an INVALID_TOKEN error when calling scheduleNormalizedPushNotificationMinutes() from cloud code. The "Send Notification" button in the BrainCloud dashboard also fails to work.

braincloud1.JPG

  1. I've correctly uploaded/configured my .p12 file etc.
  2. I'm correctly retrieving the device token from the client, and it shows up on the BrainCloud dashboard.
  3. My Apple certs/profiles etc. are in order.
                var alertContentJson = {
                    "body": "content of message",
                    "title": "message title"
                };
                var customDataJson = {
                    "field1": "value1",
                    "field2": "value2"
                };
                var minutesFromNow = 1;
                var otherPlayerId = "someId";
                var pushNotificationProxy = bridge.getPushNotificationServiceProxy();
                
                var postResult = pushNotificationProxy.scheduleNormalizedPushNotificationMinutes(otherPlayerId, alertContentJson, customDataJson, minutesFromNow);
]]>https://forums.getbraincloud.com/topic/18/invalid_token-when-sending-push-notificationsRSS for NodeMon, 18 May 2026 06:42:06 GMTTue, 28 May 2019 16:48:58 GMT60<![CDATA[Reply to 'INVALID_TOKEN' When Sending Push Notifications on Wed, 29 May 2019 17:13:31 GMT]]>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!

]]>https://forums.getbraincloud.com/post/53https://forums.getbraincloud.com/post/53Wed, 29 May 2019 17:13:31 GMT<![CDATA[Reply to 'INVALID_TOKEN' When Sending Push Notifications on Wed, 19 Jun 2019 20:16:58 GMT]]>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.
]]>https://forums.getbraincloud.com/post/97https://forums.getbraincloud.com/post/97Wed, 19 Jun 2019 20:16:58 GMT<![CDATA[Reply to 'INVALID_TOKEN' When Sending Push Notifications on Wed, 29 May 2019 17:25:51 GMT]]>Awesome - glad to hear it!

I'll mark it resolved for you.

Cheers!

Paul.

]]>https://forums.getbraincloud.com/post/54https://forums.getbraincloud.com/post/54Wed, 29 May 2019 17:25:51 GMT<![CDATA[Reply to 'INVALID_TOKEN' When Sending Push Notifications on Wed, 29 May 2019 17:13:31 GMT]]>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!

]]>https://forums.getbraincloud.com/post/53https://forums.getbraincloud.com/post/53Wed, 29 May 2019 17:13:31 GMT<![CDATA[Reply to 'INVALID_TOKEN' When Sending Push Notifications on Tue, 28 May 2019 21:29:35 GMT]]>@Joseph-Wiemer No worries - good luck! And keep us posted! 🙂

]]>https://forums.getbraincloud.com/post/52https://forums.getbraincloud.com/post/52Tue, 28 May 2019 21:29:35 GMT<![CDATA[Reply to 'INVALID_TOKEN' When Sending Push Notifications on Tue, 28 May 2019 20:57:06 GMT]]>@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.

]]>https://forums.getbraincloud.com/post/49https://forums.getbraincloud.com/post/49Tue, 28 May 2019 20:57:06 GMT<![CDATA[Reply to 'INVALID_TOKEN' When Sending Push Notifications on Tue, 28 May 2019 20:42:43 GMT]]>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...

]]>https://forums.getbraincloud.com/post/48https://forums.getbraincloud.com/post/48Tue, 28 May 2019 20:42:43 GMT<![CDATA[Reply to 'INVALID_TOKEN' When Sending Push Notifications on Tue, 28 May 2019 20:34:17 GMT]]>@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.

]]>https://forums.getbraincloud.com/post/47https://forums.getbraincloud.com/post/47Tue, 28 May 2019 20:34:17 GMT<![CDATA[Reply to 'INVALID_TOKEN' When Sending Push Notifications on Tue, 28 May 2019 20:32:16 GMT]]>@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.

]]>https://forums.getbraincloud.com/post/46https://forums.getbraincloud.com/post/46Tue, 28 May 2019 20:32:16 GMT<![CDATA[Reply to 'INVALID_TOKEN' When Sending Push Notifications on Tue, 28 May 2019 19:33:38 GMT]]>Correct! @Paul-Winterhalder Keep us updated @Joseph-Wiemer

]]>https://forums.getbraincloud.com/post/45https://forums.getbraincloud.com/post/45Tue, 28 May 2019 19:33:38 GMT<![CDATA[Reply to 'INVALID_TOKEN' When Sending Push Notifications on Tue, 28 May 2019 19:32:59 GMT]]>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?

]]>https://forums.getbraincloud.com/post/44https://forums.getbraincloud.com/post/44Tue, 28 May 2019 19:32:59 GMT<![CDATA[Reply to 'INVALID_TOKEN' When Sending Push Notifications on Tue, 28 May 2019 19:42:14 GMT]]>@Joseph-Wiemer

Can you confirm that the cert that you made was for Production? AND! that the apps entitlement was set correctly.

https://developer.apple.com/documentation/bundleresources/entitlements/aps-environment https://developer.apple.com/documentation/usernotifications/registering_your_app_with_apns

By default when building from xcode, the default Push Notification Entitlement is development, ensure this is set to production.

Have you confirmed you received the Push notification from pushtry.com on your device ?

]]>https://forums.getbraincloud.com/post/43https://forums.getbraincloud.com/post/43Tue, 28 May 2019 19:42:14 GMT<![CDATA[Reply to 'INVALID_TOKEN' When Sending Push Notifications on Tue, 28 May 2019 19:28:19 GMT]]>Okay - the two symptoms:

#1 - You say you never got that push from the pushtry tool. I assume your app wasn't running at the time? Apple hides push notifications from apps if the app is currently running. Try again?

#2 - When you say you can't send notifications, you mean they aren't received - just like #1, correct?

Talking to one of our devs now. He mentions that you need to ensure that the app that's running on the device is built with the correct "entitlements". He's gonna provide more info...

Stay tuned...

Paul.

]]>https://forums.getbraincloud.com/post/42https://forums.getbraincloud.com/post/42Tue, 28 May 2019 19:28:19 GMT<![CDATA[Reply to 'INVALID_TOKEN' When Sending Push Notifications on Tue, 28 May 2019 19:17:25 GMT]]>@Paul-Winterhalder I exported just the private key without the cert and pushtry.com now says, "Push notification sent successfully". So, I uploaded this new .p12 file to brainCloud. However, I never actually received a notification on my device, and am still unable to send notifications via the brainCloud dashboard.

]]>https://forums.getbraincloud.com/post/41https://forums.getbraincloud.com/post/41Tue, 28 May 2019 19:17:25 GMT<![CDATA[Reply to 'INVALID_TOKEN' When Sending Push Notifications on Tue, 28 May 2019 19:08:49 GMT]]>@Paul-Winterhalder That gives me something to pursue. Thanks, Paul!

]]>https://forums.getbraincloud.com/post/40https://forums.getbraincloud.com/post/40Tue, 28 May 2019 19:08:49 GMT<![CDATA[Reply to 'INVALID_TOKEN' When Sending Push Notifications on Tue, 28 May 2019 19:00:14 GMT]]>I agree with Jonathan's suggestion to recreate the P12 file. I'm reading several articles here where someone was getting the same error.

The solution in all cases was to recreate the P12 file.

The quote from the discussion:

I figured out the problem. I revoked and regenerated the certificate again, and this time I only exported the private key (without the certificate). In Keychain access, I exported as .p12 and used the new file and it worked. For some reason, PushSharp wasn't play well with .p12 when both certificate and private key are present in the file.

Here's the link to Stack Overflow:
https://stackoverflow.com/questions/23329040/pushsharp-apns-production-the-credentials-supplied-to-the-package-were-not-reco

Hope that helps!

Paul.

]]>https://forums.getbraincloud.com/post/39https://forums.getbraincloud.com/post/39Tue, 28 May 2019 19:00:14 GMT<![CDATA[Reply to 'INVALID_TOKEN' When Sending Push Notifications on Tue, 28 May 2019 18:58:46 GMT]]>@Paul-Winterhalder That's what I thought at first, but no, my password is correct.

]]>https://forums.getbraincloud.com/post/38https://forums.getbraincloud.com/post/38Tue, 28 May 2019 18:58:46 GMT<![CDATA[Reply to 'INVALID_TOKEN' When Sending Push Notifications on Tue, 28 May 2019 18:48:16 GMT]]>@Joseph-Wiemer My guess would be bad password?

]]>https://forums.getbraincloud.com/post/37https://forums.getbraincloud.com/post/37Tue, 28 May 2019 18:48:16 GMT<![CDATA[Reply to 'INVALID_TOKEN' When Sending Push Notifications on Tue, 28 May 2019 18:45:13 GMT]]>If it is a cert issue. These steps may help: https://www.mobiloud.com/help/knowledge-base/how-to-export-push-notification-certificate-p12/

edit: this link seems to confirm the cert theory. Based on the error message: https://stackoverflow.com/questions/22568648/ios-production-push-notifications-invalid-token-from-apns-server

]]>https://forums.getbraincloud.com/post/36https://forums.getbraincloud.com/post/36Tue, 28 May 2019 18:45:13 GMT<![CDATA[Reply to 'INVALID_TOKEN' When Sending Push Notifications on Tue, 28 May 2019 18:31:15 GMT]]>@Paul-Winterhalder I'm getting "The credentials supplied to the package were not recognized." No clue what that means, unfortunately.

]]>https://forums.getbraincloud.com/post/35https://forums.getbraincloud.com/post/35Tue, 28 May 2019 18:31:15 GMT<![CDATA[Reply to 'INVALID_TOKEN' When Sending Push Notifications on Tue, 28 May 2019 18:29:16 GMT]]>Adding in, when we get an error using the device token, we remove it from memory on the brainCloud portal, to prevent spamming the system with bad tokens. So if you look under user Monitoring | User Monitoring | User Summary you won't see the deviceTokens on that profile (due to the error your reporting.)

That said, your registration implementation and device token look fine. I don't think it's an issue with the token.

So perhaps it's an issue with the cert?

On the iCloud dashboard, I would check to ensure the cert used and uploaded with brainCloud had push notifications enabled.

373168e8-de27-46b5-bb9e-eb0a659a3e77-image.png

]]>https://forums.getbraincloud.com/post/34https://forums.getbraincloud.com/post/34Tue, 28 May 2019 18:29:16 GMT<![CDATA[Reply to 'INVALID_TOKEN' When Sending Push Notifications on Tue, 28 May 2019 18:20:34 GMT]]>Hi Joseph,

Here's a way to test your Push notification setup (outside of brainCloud) to ensure that the cert and token retrieval is configured properly:

  1. Go to pushtry.com
  2. Upload the same .p12 file that you're using for brainCloud. Be sure to enter the password too.
  3. Grab the Device Token(s) that you see in the user's User Summary Page - copy those over, separated by commas
  4. Production box accordingly (brainCloud always tries to send to Production first, if that fails, sends to Sandbox)
  5. Enter a test message
  6. Hit [Send]

We just tried this with one of our test apps and it worked well. Does it work for your setup?

]]>https://forums.getbraincloud.com/post/33https://forums.getbraincloud.com/post/33Tue, 28 May 2019 18:20:34 GMT<![CDATA[Reply to 'INVALID_TOKEN' When Sending Push Notifications on Tue, 28 May 2019 17:36:21 GMT]]>@Paul-Winterhalder Thanks, Paul.

]]>https://forums.getbraincloud.com/post/32https://forums.getbraincloud.com/post/32Tue, 28 May 2019 17:36:21 GMT<![CDATA[Reply to 'INVALID_TOKEN' When Sending Push Notifications on Tue, 28 May 2019 17:27:58 GMT]]>Hi Joseph,

We're looking into it. That error would generally indicate that the push token itself is invalid (though looking at the details in your logs it looks fine) - or that for some reason, the token isn't valid for that particular .p12 cert that you've uploaded to brainCloud).

We'll have more recommendations soon...

Paul.

]]>https://forums.getbraincloud.com/post/31https://forums.getbraincloud.com/post/31Tue, 28 May 2019 17:27:58 GMT