Skip to content

fix(client): name Chromium's push AbortError (0.1.3) - #1

Merged
ralyodio merged 1 commit into
mainfrom
fix/push-abort-reasons
Sep 24, 2026
Merged

ralyodio merged 1 commit into
mainfrom
fix/push-abort-reasons

Conversation

@ralyodio

Copy link
Copy Markdown
Contributor

subscribe() passed Chromium's raw Registration failed - push service error through, which looks like an app failure. It means the browser has no reachable push service: ungoogled-chromium has none at all (reported on agenticjobs.work), and Brave ships with Use Google services for push messaging off.

  • AbortError → PushError('no-push-service'), or 'brave-push-off' with the exact brave://settings/privacy fix when navigator.brave exists
  • Chromium's AbortError Registration failed - permission denied (seen in headless Chrome) → 'denied'
  • types + README updated; new test covers all three; 18/18 pass
  • version 0.1.3 (the release triggers publish.yml)

Same mapping shipped in agenticjobs 0.20.2 (profullstack/agenticjobs#188).

🤖 Generated with Claude Code

…ission)

subscribe() re-threw Chromium's raw 'Registration failed - push service
error', which reads like the app failed. It means the browser has no reachable
push service: ungoogled Chromium has none, Brave ships with it off. Map it to
PushError 'no-push-service' / 'brave-push-off' (with the brave://settings
fix), and Chromium's AbortError 'permission denied' to 'denied'. 0.1.3.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@ralyodio
ralyodio merged commit 12b9f3d into main Sep 24, 2026
2 checks passed
@ralyodio
ralyodio deleted the fix/push-abort-reasons branch September 24, 2026 10:10
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

Successfully merging this pull request may close these issues.

1 participant