-
-
Notifications
You must be signed in to change notification settings - Fork 852
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
Any way to get bad/invalid device tokens? #109
Comments
Same question about GCM. Maybe add a callback to reporting about bad tokens? |
APNS has (had?) a feedback channel and GCM already sends the invalid tokens directly back in the response - one has to check the |
To get APNS bad tokens I made a pull request - #175 |
Can be a callback method via post custom method?
Or via amqp\nsq or ws? |
I will implement the sync mode so you can get error message from fail push notification in API response. cc @MrChenhao |
Release v1.8.1 https://github.com/appleboy/gorush/releases/tag/v1.8.1 If you need error logs from sending fail notifications, please set core:
port: "8088" # ignore this port number if auto_tls is enabled (listen 443).
worker_num: 0 # default worker number is runtime.NumCPU()
queue_num: 0 # default queue number is 8192
max_notification: 100
- sync: false
+ sync: true See the following error format. {
"counts": 60,
"logs": [
{
"type": "failed-push",
"platform": "android",
"token": "*******",
"message": "Hello World Android!",
"error": "InvalidRegistration"
},
{
"type": "failed-push",
"platform": "ios",
"token": "*****",
"message": "Hello World iOS1111!",
"error": "Post https://api.push.apple.com/3/device/bbbbb: remote error: tls: revoked certificate"
},
{
"type": "failed-push",
"platform": "ios",
"token": "*******",
"message": "Hello World iOS222!",
"error": "Post https://api.push.apple.com/3/device/token_b: remote error: tls: revoked certificate"
}
],
"success": "ok"
} |
The APNS HTTP/2 will report bad/invalid device tokens. I think we should removed those invalid tokens from DB to prevent from sending them again and again.
Is there a way to get those from gorush API?
Thanks
The text was updated successfully, but these errors were encountered: