Skip to content

Preserve thread text when offline saves are partial - #36

Merged
CHOS1N11111 merged 2 commits into
mainfrom
fix/saved-thread-text-fallback
Aug 27, 2026
Merged

CHOS1N11111 merged 2 commits into
mainfrom
fix/saved-thread-text-fallback

Conversation

@CHOS1N11111

@CHOS1N11111 CHOS1N11111 commented Aug 27, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

  • persist the currently displayed main post and loaded replies before additional network work
  • keep successfully fetched replies and nested replies when individual pages fail
  • skip failed media items while retaining the text snapshot and marking the save as partial
  • preserve an existing saved version when an update cannot improve it
  • store partial-capture status in a backward-compatible snapshot format and surface it in offline reading

Root cause

The previous save flow fetched every reply and nested reply, downloaded every requested media item, and only then wrote the snapshot. Any request, consistency check, media download, or size failure discarded the entire operation even when the main-post text was already visible.

Testing

  • added coverage for visible-content baselines, missing main-post ids, partial status round trips, v2 compatibility, result messages, and best-effort request/media policies
  • GitHub Actions passed unit tests, release lint, debug/release APK builds, release AAB build, and release output verification
  • local Windows Gradle execution remains blocked before project configuration by a Java loopback connection error

@CHOS1N11111 CHOS1N11111 self-assigned this Aug 27, 2026
@CHOS1N11111
CHOS1N11111 merged commit e19815f into main Aug 27, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants