Skip to content

Instantly share code, notes, and snippets.

View bluespore's full-sized avatar
👾
[object Object]

Sean Bullock bluespore

👾
[object Object]
View GitHub Profile
@bluespore
bluespore / .transfer-errorboundary-test-scenarios.md
Last active July 2, 2026 06:11
Transfer screen ErrorBoundary repro & regression test scenarios

Transfer screen — ErrorBoundary repro scenarios

Shared test checklist for investigating the Transfer tab crash (An unexpected error occurred. Try again).

Context: A typed amount committed before both source and destination are selected may not have been written to the transfer store (only local input state + a pending ref). A later unsigned-tx hydrate or edit can desync the controlled input and hit the root ErrorBoundary. PR #801 addresses this with optimistic store updates.

What counts as a hit: Root ErrorBoundary UI (not a toast, not LogBox-only in dev). In staging/production, check Sentry for ErrorBoundary events.

Noise (usually not the bug): [RemoteTextInput] ... perform input operation requires a valid sessionID — common iOS simulator keyboard log; does not by itself mean ErrorBoundary.