errors: Add 103010 "Push recipient endpoint invalid" - #366
Merged
Merged
Conversation
Reported when a web push notification cannot be sent because the endpoint in the device's push recipient is not one Ably will send to: it has to be an https address that resolves to a publicly reachable host, and Ably does not follow a redirect away from it. Until now the realtime push worker reported such a refusal as 103004, which is registered as the provider having rejected the notification, and so named the wrong party: the notification never reached a push service. Signed-off-by: Lewis Marshall <lewis.marshall@ably.com> Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
zknill
approved these changes
Sep 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Registers a code for a web push notification that is not sent because the endpoint in the device's push recipient is not one Ably will send to: it has to be an https address that resolves to a publicly reachable host, and Ably does not follow a redirect away from it.
That refusal was reported as 103004, which is registered as
push_notification_rejected_by_provider— "the provider (APNs, FCM, or WebPush) rejected the request due to a problem with the payload or delivery parameters". In these cases nothing reached a push service, so the code named the wrong party and sent the reader to look at the payload rather than at the device registration. AtargetUrlthat cannot be decoded moves onto the new code too; that was reported as 103000 with a 500, blaming Ably for data the client supplied.The registration is left usable rather than disabled when this occurs, since a blocked address reflects what the endpoint's name resolved to at that moment, so the page says the error recurs until the registration is replaced.
🤖 Generated with Claude Code