-
-
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
Add callback or chan for failed pushes #386
Comments
There is a sync mode available that should allow for getting error feedback, see: #109. Though, I do not fully comprehend the design choice of having to switch to synchronous mode in order to be able to obtain feedback. A few points:
All in all, a method of obtaining error feedback in asynchronous mode is required. It could be as simple as introducing a new error feedback endpoint that, when queried, returns the feedback collected since the previous call to the endpoint. This way, no complicated callback mechanism would be required. Update: FWIW, to tackle this I rolled my own over at https://gitlab.com/pennersr/shove |
Maybe I can add the feature to support webhook that receive the notification log if fail. |
Hi @appleboy i ve pushed a PR if you wana check it. |
closed via #414 |
Hi,
Add the callback or chan with error and token for the failed push notification(apns and fcm).
For example when you make notification with multiple tokens and some tokens is "BadDeviceToken", I can't handle these requests. PushToIOS or PushToAndroid - return only bool value
The text was updated successfully, but these errors were encountered: