Skip to content

Force-upgrade flow with graceful rehydrate #300

Description

@kilodesodiq-arch

Problem Statement. ForceUpgradeScreen exists but the data path
(UpdateProvider) is not tested for unexpected token expiry.

Technical Context.
app/mobile/App.tsx,
new app/mobile/src/contexts/UpdateContext.tsx (assumed).

Expected Outcome. When the manifest pointer returns 401 because the token is stale,
the app re-authenticates and refreshes. No manual app restart required.

Acceptance Criteria.

  • Integration test simulates stale token → app refreshes transparently.

Files or modules likely to be affected.
app/mobile/src/contexts/UpdateContext.tsx.

Difficulty. Medium
Estimated effort. M



Backlog item #92 from `docs/maintainer-issue-backlog.md.

Metadata

Metadata

Assignees

Labels

GrantFox OSSIssue tracked in GrantFox OSSMaybe RewardedIssue may be eligible for a GrantFox rewardOfficial Campaign | FWC26Campaign: Official Campaign | FWC26area:mobileMobile (Expo / React Native) areakind:reliabilityBacklog label: kind:reliability

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions