We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It would be nice to implement a retry (exponential backoff) system for failed batched notifications.
For non-batched notifications, it would be necessary to throw an exception or dispatch an event when the notification fails.
We talk about a failed notification when the payload is valid but Expo returns with a error status.
error
When the payload is invalid, Expo returns a body containing errors field and the Service throw an ExpoNotificationsException.
errors
ExpoNotificationsException
Also, we could consider dispatching an event when a Ticket or Receipt is in error status.
The text was updated successfully, but these errors were encountered:
JamesHemery
No branches or pull requests
It would be nice to implement a retry (exponential backoff) system for failed batched notifications.
For non-batched notifications, it would be necessary to throw an exception or dispatch an event when the notification fails.
We talk about a failed notification when the payload is valid but Expo returns with a
error
status.When the payload is invalid, Expo returns a body containing
errors
field and the Service throw anExpoNotificationsException
.Also, we could consider dispatching an event when a Ticket or Receipt is in
error
status.The text was updated successfully, but these errors were encountered: