Subscription Successful, Push Fails

Answered

Comments

3 comments

  • Avatar
    Oleg Zhukov

    Hello,

    Could you please check the Push History? Am I correct that you are getting an "Invalid token" error?

    The "Invalid Token" error usually points to the mismatch between push certificate from your Control Panel and the provisioning profile that your application build is signed with. For example your application in Control Panel is configured with production push certificate, while the app build is signed with development provisioning profile, or vice versa. Could you please double check this?

    The issue also occurs in case push certificate and provisioning profile have bundle IDs that do not correspond to each other.

  • Avatar
    Guven James B

    Thanks for the response Oleg. I have just noticed the 'Invalid token' error in the Push History. The error is only displayed for the first push to a device. The subsequent pushes don't have any errors even though delivery fails. The problem ended up being about the development provisioning profile. Pushwoosh can't seem to send Sandbox push notifications for some reason. Even though I select 'Sandbox', Pushwoosh only sends Production push notifications. So, I have written a little Python script that sends push notifications instead of Pushwoosh.

  • Avatar
    Oleg Zhukov

    Hello,

    Please note, that is not enough to just press the "Sandbox" button in your Control Panel if previously the "Production" gateway was chosen. You need to reconfigure the app (upload the certificate one more time) and choose required gateway.

Please sign in to leave a comment.