Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BadDeviceTokenThe specified device token was bad. Verify that the request contains a valid token and that the token matches the environment #142

Open
gienmangaliman opened this issue Jun 8, 2021 · 3 comments

Comments

@gienmangaliman
Copy link

gienmangaliman commented Jun 8, 2021

Hi! Good morning! Where should I verify that the request contains a valid token and that the token matches the environment ?

I'm using the device token generated when I grant the safari browser to send me notification. Looking forward for a little help here. thank you!

I'm using this for safari macOS web push notification btw 😃

@nomorobo-vehikl
Copy link

I am seeing a similar issue intermittently, our iOS team has verified that the token we're using is correct for our sandbox environment, but we still get a 400. We don't get this error consistently, or at least not in a way we can see.

@ryoutarou-hyoudou
Copy link

I'm seeing the same issue. I'm trying to send push notificaiton to app from staging with pem file for production.

@ryoutarou-hyoudou
Copy link

In my case, the boolean value $isProductionEnv didn't match the certificate I was using.
https://github.com/edamov/pushok/blob/master/src/Client.php#L82

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants