Skip to content

Android: recover books and covers when file access is lost - #9

Merged
EL4CTEO merged 1 commit into
mainfrom
claude/ecstatic-keller-lowbbm
Sep 28, 2026
Merged

EL4CTEO merged 1 commit into
mainfrom
claude/ecstatic-keller-lowbbm

Conversation

@EL4CTEO

@EL4CTEO EL4CTEO commented Sep 28, 2026

Copy link
Copy Markdown
Owner

Fixes

Opening the app could land on "The file can't be found", and books
could show no cover, whenever ReadArea couldn't read a file it had in
its library: after a reinstall restored the library from backup (which
brings back the database but not file access or cover images), after
access to all files or to a folder was withdrawn, or when Android
dropped the permission of books added one by one.

- A book whose file can't be opened right now is no longer marked as
  done with no cover; its details and cover are read on a later scan.
- Covers whose images are gone from app storage are read again.
- The last book is only reopened at start if it can be read; otherwise
  the app opens on the library.
- Books ReadArea can no longer open are set aside instead of failing
  when tapped, and come back when access returns: the device-wide
  search asks for access again, and a folder whose access was lost
  prompts to choose it again (new strings in all 17 languages).
- Covers can be as large as other book entries (32 MB) instead of the
  6 MB used for details, for high-resolution light novel covers.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NY4ECaovvxsqYYRS2RrEhb
@EL4CTEO
EL4CTEO merged commit daf4e33 into main Sep 28, 2026
14 checks passed
@EL4CTEO
EL4CTEO deleted the claude/ecstatic-keller-lowbbm branch September 28, 2026 12:05
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