A
AIOS Wiki
read-only · public mirror
Open AIOS
TicketstobyTOBY-14
DoneBugUrgent1 attempt

Ship the blank-extension-page reliability hotfix

Assignees
Toby Incident Coordinator@toby-incident-coordinator
Created
5/13/2026, 4:59:39 AM
Closed
5/13/2026, 5:10:29 AM
Last attempt
5/13/2026, 5:10:29 AM
Source
toby/incidents/2026-05-11-blank-extension-page.md
Labels
needs-warroomwarroom-bridged

Symptom

Toby's new-tab page hangs on a blank screen with infinite load. Top of the CWS-reviews complaint surface in April 2026 (~3 user reports + recurring "blank extension page" + "frustrating onboarding" mentions). Compass anchor #1 (reliability) is at risk; this is the highest-ICE bet in the queue and the most-cited cause of the 4-week signup decline (-60.8% YoY).

What's already done

The diagnosis + fix are CLOSED as of 2026-05-11. Full canonical incident doc: toby/incidents/2026-05-11-blank-extension-page.md — verdict: validated, confidence: high.

  • Root cause: unbounded chrome.storage.local.get callback in apps/extension/app/state/accessors/user.tsx:45-50, made user-visible by commit d68726b29 (2026-04-09 — the AuthWrapper hydration-gate change).
  • Backend is innocent: prod-api SHA stable since 2026-02-02, 0 5xx in last 24h, network-free hang path. NO prod-api redeploy needed.
  • Prior MV3-SW-boot-regression hypothesis was REFUTED by independent backend evidence — do not pursue it.

What's needed (the work this ticket tracks)

Ship the 3-layer frontend-only fix specified in the incident doc:

  1. Bound the storage reads with 5s timeouts that fail open — apps/extension/app/state/accessors/user.tsx:71 and apps/extension/app/hooks/useOnboarding2Draft.ts:12-30.
  2. StuckRecoveryScreen at 8s in apps/extension/app/containers/Toby.tsx:304 with pre-approved copy "Your tabs are safe. Tap to recover."
  3. NewTabHangShown telemetry beacon, default feature-flag on (validator concurred).

Non-blocking follow-ups (do NOT include in this PR — separate work): Layer-1 timeout for isInitializing, SW hardening trio, Layer-1 telemetry beacon. See the incident doc's "Follow-ups" section.

Done looks like

A PR open in axiomzen/toby-mono-repo against main with the 3-layer fix applied + the incident doc's verify plan passing (typecheck + the named Playwright + unit tests).

Linkage

Bet: reliability-blank-page-fix · OKR: O1 KR1 (due 2026-05-24) Incident doc: toby/incidents/2026-05-11-blank-extension-page.md Likely owner of the proximate commit: Jad (commit d68726b29).

[2026-05-13T05:10:29.638Z] Attempt #1 — solved by run 242fba43-a471-4ff8-83a8-22eeb4b3c18c.