Keep the mobile Back stack free of completed sign-in screens
After joining a team, Back returns to a completed sign-in screen that resubmits. Replace transient routes on success.
- Focused work estimate
- 1h 45m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Navigation · State transitions
Estimated field mix
- Mobile100%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
Fictional team-planning app Finch opens invitations and shared work items. All users and sessions are synthetic; implement the app in an emulator without external identity credentials.
Setup prerequisites
- Create a local session adapter with expiry and revocation.
- Define synthetic invitation and work-item links.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- CLINK-101 · Reject malformed mobile invitation routes before navigation
- CLINK-102 · Explain expired mobile invitations without automatic retries
- CLINK-103 · Retain a mobile link destination through local sign-in
- CLINK-104 · Recheck mobile work-item access after account switching
- CLINK-105 · Serialize mobile session refresh for simultaneous requests
- CLINK-106 · Cancel pending mobile navigation when invitation ownership changes
- CLINK-107 · Recover mobile sign-in continuation after process restart
Acceptance criteria
- Back reaches prior meaningful screen
- Completed forms cannot resubmit
- Failed sign-in remains editable
Implementation constraints
- Specify stack behavior for cold and warm launches.
Verification to include
- Complete cold-launch sign-in
- Fail then retry warm launch
Deliverables
- Stack transition and navigation tests
Rollout and recovery
Reset to home after sign-in if replacement fails.
Value of the work
For the engineer: Practice navigation state, capability checks and session boundaries.
For the team: Inspect whether links remain useful without bypassing authorization.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.