Verify Android OAuth cold-start fix on a real device (#300 follow-up) #388
Labels
No labels
area:auth
area:ci
area:db
area:infra
area:native
area:pwa
area:service
epic
feature
foundation
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
james/carol#388
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up to #300 (PR #383, merged). The cold-start fix — draining the OAuth deep-link queue at bootstrap when the OS killed the app during the browser handoff — is fully unit-tested (idempotency, single exchange, no double-exchange) but could not be verified headlessly. The client vitest runner is node-env with no RN render or real Activity lifecycle, so the actual cold-relaunch path is unexercised.
What to verify on-device
On a physical Android device (or emulator) running the signed build:
carol://auth/oauth/completedeep link relaunches the app cold./chat, signed in (not bounced back to/login).Notes
app/_layout.tsx(Linking.getInitialURL()branch),lib/auth/oauthColdStart.ts,lib/auth/oauthDeepLink.ts(drainOauthDeepLink).new URL("carol://…")mis-parses custom schemes — see #298. Watch for any regression in deep-link parsing while testing.