Fix offline session recovery and add animated retry states - #177
Merged
Conversation
This was referenced Sep 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Returning users can now open cached content while authentication refresh is delayed or offline. Unavailable screens show a consistent animated cloud and a Try again action, and authentication forms show clear connection advice instead of raw transport errors.
Closes #166. Closes #167.
Validation: clean install, 10 regression tests (
npm test, Node 24),npm run typecheck, and Android/web production exports passed. Browser checks with mocked services passed for expired-session cached browsing; uncached offline states in Today, History, Saved, Stats, and Personalization; topic/Today/detail recovery after reconnecting; dark theme with reduced motion; and friendly offline sign-in errors. No uncaught browser errors occurred. Physical-device validation is still needed; no live backend or production data was used.This PR targets
developand preserves its individual commits. App version and native runtime are unchanged. After merge, release preparation can add the version bump and eligible one-time What's New entry before thedeveloptomainPR.