feat(android): Phase 1 viewer actions — favorite, share, download, trash, info sheet #1116

Merged
chris merged 3 commits from ux-android-viewer-actions into main 2026-10-11 16:59:26 +02:00
Owner

Spec 055 task T005 (Phase 1 viewer actions). Builds on Phase 0 PR #1112 and the Phase 0 IA shell PR #1114.

What you get

A second row in the viewer chrome, directly under the existing top bar and wearing the same 80% black scrim so the two rows read as one block:

favorite · share · save · details · trash

The actions are spread evenly rather than packed left — the row is an action bar, and its width changes with how many actions the current item actually has (the save button disappears when there is nothing to save). A bottom bar was considered and rejected: it would sit on top of the video controls row, which would have meant threading state between two unrelated composables to stop them colliding.

Favorite flips optimistically and reverts with a Retry action if the server disagrees. Tapping the heart before that item's detail has ever been loaded fetches the detail first rather than guessing — otherwise the first tap on an already-favorited photo would appear to do nothing, because the client would assume "not a favorite" and POST a value that was already true.

Share hands the Android share sheet the photo file (staged from the preview rendition and delivered through a FileProvider); videos, and any photo that cannot be staged, fall back to the web media page ({serverUrl}/media/{id}). See "Decisions" below.

Save downloads the preview rendition into Pictures/Memories through MediaStore. minSdk 29 means scoped storage, so there is no runtime permission to request; the row is held IS_PENDING until the bytes are fully written, so a failed save never leaves a half-written entry visible in the gallery. Progress shows as a pill stacked under the snackbar, and both live outside the chrome so a save outlives a chrome hide. The save button is hidden when previewUrl is absent — a button that can only fail is worse than no button.

Trash asks for confirmation in plain language first ("Es landet zuerst im Papierkorb und kann wiederhergestellt werden."), then POSTs, then shows "Zum Papierkorb verschoben" with an Undo action that restores. The item is dropped from the pager so the next photo slides into its place. If that empties the list — one photo in the whole album — the screen holds on the empty state until Undo resolves instead of navigating away with the snackbar still up.

Info is a bottom sheet that renders only fields the payload actually carries: capture date, duration, title, description, things. No dashes for missing data, no placeholders, no raw JSON, no internal field names.

Findings that shaped the implementation

1. The OpenAPI document is wrong about trash and restore. It advertises 200 + MediaDetail. The controller is annotated @ResponseStatus(NO_CONTENT), so the running server answers 204 with an empty body — and the web client already types both as void. A client generated from the spec would try to decode a body that never arrives. The app is implemented against observed behaviour (executeEmpty(): any 2xx, body ignored), and HttpMediaActionsApiTest pins that. Filed as ISSUE-116; the fix belongs to the API spec, not the app.

2. MediaDetail carries things but no persons/faces. The info sheet therefore cannot say who is in a photo, even though faces and person names exist server-side. Rather than invent a row, it simply does not offer one. Filed as ISSUE-117.

3. No original file is downloadable. There is no user-facing /api/media/{id}/original controller (OpenAPI marks it "not currently exposed"; only the worker-scoped variant exists) and video_preview reports video_preview_not_implemented. Saving the original is therefore impossible today — the same gap already recorded as ISSUE-115. The Save action saves the preview rendition only, and says so in the PR text rather than pretending otherwise. Once an original-stream endpoint lands, extending this is a one-method change in MediaDownloader.

Decisions worth a second look

Share target. Revised after review. The product decision is that recipients may have no account and no route to the server, so sharing must hand them the actual picture — the standard family UX, like Google Photos. Photos are therefore fetched into cacheDir/share/ and passed to ACTION_SEND as a content uri from a FileProvider (authority ${applicationId}.share, FLAG_GRANT_READ_URI_PERMISSION); the bytes are written under a .part name and renamed into place, so a racing tap can never publish a truncated JPEG, and only that one subdirectory is exposed to foreign apps. The decision lives in ShareTarget.kt#decideShareTarget — a pure function, unit-tested — rather than inside the ViewModel, so photo/video/failure can be exercised without Android types. Videos keep URL-text sharing because no video rendition exists yet (ISSUE-115), with a snackbar telling the sender recipients must be signed in; a photo that fails to stage, or a FileProvider path that is refused, falls back to the same {serverUrl}/media/{id} link with a note, so a share tap is never a dead end. previewUrl was never a viable link target: it sits behind bearer auth, so a recipient would hit a login wall.

Chrome layout. Second actions row instead of a bottom bar, for the reason given above.

MediaViewerViewModel holds no Context. It emits typed ViewerEvent/ViewerMessageKind values through a channel and the screen resolves them against resources. That keeps the whole optimistic-favorite / trash / retry / restore logic JVM-testable, and it is why the screen owns a local SnackbarHostState — the viewer is full-bleed black, so the app-level snackbar would have sat behind the bottom nav.

Favorite state resolution. favorites[id] ?: details[id]?.favorite ?: false, with the user's own in-flight choice always winning over a detail response that is racing it. A detail response never clobbers a key the user has already set.

Scope discipline

ui/MemoriesApp.kt changes by four lines (one import, one viewModel(), two parameters), to stay clear of the concurrent nav-shell lane. TimelineViewModel gained removeItem(id), which only touches the loaded list — pagination reads the stored cursor, not the list, so removing the last loaded item cannot stall the timeline (pinned by a test).

Verification

./gradlew :app:testDebugUnitTest :app:assembleDebug   # BUILD SUCCESSFUL, 154 tests, 0 failures

New coverage:

  • HttpMediaActionsApiTest — MockWebServer contract tests for the five endpoints: paths, bearer headers, the metadataClass/value body, 204-empty for trash/restore, 403 → ForbiddenApiException, 401 → UnauthorizedApiException.
  • MediaViewerViewModelTest — detail load (once, seeding favorite + absolute URLs, non-blocking), optimistic favorite while in flight, unfavorite-via-DELETE, the first-tap fetches-first regression guard, favorite failure → revert + working retry, forbidden → owner-only, trash/restore event flow, trash retry, download progress + bearer token + failure + no-preview, share link, filename, plus the share flow (photo staged → ShareReady, staging failure → link fallback, video → link without staging, no-preview → link, no-link + no-preview → nothing, missing session → re-login, in-flight debounce).
  • ShareTargetTest — the pure share-target decision: photo → file, unknown type → photo, video → link with or without a rendition, blank preview → link, photo can still stage without a known link, Nothing when neither is available, and web-link normalisation.
  • TimelineViewModelTest — removeItem shifts the following item into place, ignores unknown ids, does not stall load-more.
  • ViewerDateTest — duration formatting and its null/zero/negative cases.

All user-visible strings are in values/ (German), values-en/, values-da/; keys and format placeholders verified consistent across the three locales.

Risks

  • Trashing the only loaded item briefly leaves a black screen with just the Undo snackbar. Correct by design, but it is a state we only reach with a one-photo album — worth a manual look.
  • Share target is now the file itself (see "Decisions"). The link path survives only as fallback, so reverting to link-only sharing is a one-line change in decideShareTarget. Note the wording when a photo fails to stage says the link was shared while the photo could not be prepared — accurate, but the recipient then gets a link rather than the picture.
  • ShareIntent.Nothing reuses viewer_no_preview_save. Reachable only when there is no session link and no rendition (effectively logged out), and its wording says "save" rather than "share". Cosmetic and near-unreachable; a dedicated string would fix it if anyone minds.
  • Two snackbars can queue. The event loop is deliberately sequential (one message at a time reads calmer than stacked toasts), so a message raised while the Undo snackbar is still on screen waits for it. The Undo window is Long, so that wait can be a few seconds.
  • Device-local download naming is memories-{mediaItemId}.jpg, which is stable and collision-free but not human-readable. Deliberate: it avoids guessing at a title the server may not have.

Follow-up commit: share the photo file

Second commit on this branch, addressing the share-target risk above.

  • media/MediaShareCache.kt + media/AndroidShareCache.kt — stages a rendition into cacheDir/share/ via .part-then-rename, so no partially written file is ever handed out.
  • media/RenditionHttp.kt — the HTTP rendition fetch factored out of AndroidMediaDownloader and shared by save and share, so the two paths cannot drift.
  • ui/timeline/ShareTarget.kt — decideShareTarget() / shareWebLink() / shareFileName(), the testable decision.
  • res/xml/file_paths.xml + a FileProvider entry in AndroidManifest.xml exposing only cache-path "share".
  • MediaViewerViewModel — sharing / preparing state, ShareReady and ShareLink events; shareText now delegates to shareWebLink.
  • MediaViewerScreen — the progress pill reads downloads ?: preparing and labels itself accordingly (the save icon no longer shows busy while a share is preparing), shareFile() builds the ACTION_SEND, and startChooser() is shared with the text path.
  • Strings viewer_share_preparing / viewer_share_video_link / viewer_share_link_fallback in de, en and da.

Verification for this commit: ./gradlew :app:testDebugUnitTest :app:assembleDebug — BUILD SUCCESSFUL, 154 tests, 0 failures, APK assembled. CI on the PR: Android unit tests and debug APK success, Run scoped PR tests success, non-Android scopes correctly skipped.

Not merged — left for orchestrator review.

Spec 055 task **T005** (Phase 1 viewer actions). Builds on Phase 0 PR #1112 and the Phase 0 IA shell PR #1114. ## What you get A second row in the viewer chrome, directly under the existing top bar and wearing the same 80% black scrim so the two rows read as one block: **favorite · share · save · details · trash** The actions are spread evenly rather than packed left — the row is an action bar, and its width changes with how many actions the current item actually has (the save button disappears when there is nothing to save). A bottom bar was considered and rejected: it would sit on top of the video controls row, which would have meant threading state between two unrelated composables to stop them colliding. **Favorite** flips optimistically and reverts with a Retry action if the server disagrees. Tapping the heart before that item's detail has ever been loaded fetches the detail first rather than guessing — otherwise the first tap on an already-favorited photo would appear to do nothing, because the client would assume "not a favorite" and POST a value that was already true. **Share** hands the Android share sheet the photo *file* (staged from the preview rendition and delivered through a FileProvider); videos, and any photo that cannot be staged, fall back to the web media page (`{serverUrl}/media/{id}`). See "Decisions" below. **Save** downloads the preview rendition into `Pictures/Memories` through MediaStore. minSdk 29 means scoped storage, so there is no runtime permission to request; the row is held `IS_PENDING` until the bytes are fully written, so a failed save never leaves a half-written entry visible in the gallery. Progress shows as a pill stacked under the snackbar, and both live outside the chrome so a save outlives a chrome hide. The save button is hidden when `previewUrl` is absent — a button that can only fail is worse than no button. **Trash** asks for confirmation in plain language first ("Es landet zuerst im Papierkorb und kann wiederhergestellt werden."), then POSTs, then shows "Zum Papierkorb verschoben" with an **Undo** action that restores. The item is dropped from the pager so the next photo slides into its place. If that empties the list — one photo in the whole album — the screen holds on the empty state until Undo resolves instead of navigating away with the snackbar still up. **Info** is a bottom sheet that renders only fields the payload actually carries: capture date, duration, title, description, things. No dashes for missing data, no placeholders, no raw JSON, no internal field names. ## Findings that shaped the implementation **1. The OpenAPI document is wrong about trash and restore.** It advertises `200 + MediaDetail`. The controller is annotated `@ResponseStatus(NO_CONTENT)`, so the running server answers **204 with an empty body** — and the web client already types both as `void`. A client generated from the spec would try to decode a body that never arrives. The app is implemented against observed behaviour (`executeEmpty()`: any 2xx, body ignored), and `HttpMediaActionsApiTest` pins that. Filed as **ISSUE-116**; the fix belongs to the API spec, not the app. **2. `MediaDetail` carries `things` but no persons/faces.** The info sheet therefore cannot say who is in a photo, even though faces and person names exist server-side. Rather than invent a row, it simply does not offer one. Filed as **ISSUE-117**. **3. No original file is downloadable.** There is no user-facing `/api/media/{id}/original` controller (OpenAPI marks it "not currently exposed"; only the worker-scoped variant exists) and `video_preview` reports `video_preview_not_implemented`. Saving the original is therefore impossible today — the same gap already recorded as **ISSUE-115**. The Save action saves the preview rendition only, and says so in the PR text rather than pretending otherwise. Once an original-stream endpoint lands, extending this is a one-method change in `MediaDownloader`. ## Decisions worth a second look **Share target.** *Revised after review.* The product decision is that recipients may have no account and no route to the server, so sharing must hand them the actual picture — the standard family UX, like Google Photos. Photos are therefore fetched into `cacheDir/share/` and passed to `ACTION_SEND` as a content uri from a `FileProvider` (authority `${applicationId}.share`, `FLAG_GRANT_READ_URI_PERMISSION`); the bytes are written under a `.part` name and renamed into place, so a racing tap can never publish a truncated JPEG, and only that one subdirectory is exposed to foreign apps. The decision lives in `ShareTarget.kt#decideShareTarget` — a pure function, unit-tested — rather than inside the ViewModel, so photo/video/failure can be exercised without Android types. Videos keep URL-text sharing because no video rendition exists yet (ISSUE-115), with a snackbar telling the sender recipients must be signed in; a photo that fails to stage, or a `FileProvider` path that is refused, falls back to the same `{serverUrl}/media/{id}` link with a note, so a share tap is never a dead end. `previewUrl` was never a viable link target: it sits behind bearer auth, so a recipient would hit a login wall. **Chrome layout.** Second actions row instead of a bottom bar, for the reason given above. **`MediaViewerViewModel` holds no Context.** It emits typed `ViewerEvent`/`ViewerMessageKind` values through a channel and the screen resolves them against resources. That keeps the whole optimistic-favorite / trash / retry / restore logic JVM-testable, and it is why the screen owns a local `SnackbarHostState` — the viewer is full-bleed black, so the app-level snackbar would have sat behind the bottom nav. **Favorite state resolution.** `favorites[id] ?: details[id]?.favorite ?: false`, with the user's own in-flight choice always winning over a detail response that is racing it. A detail response never clobbers a key the user has already set. ## Scope discipline `ui/MemoriesApp.kt` changes by **four lines** (one import, one `viewModel()`, two parameters), to stay clear of the concurrent nav-shell lane. `TimelineViewModel` gained `removeItem(id)`, which only touches the loaded list — pagination reads the stored cursor, not the list, so removing the last loaded item cannot stall the timeline (pinned by a test). ## Verification ``` ./gradlew :app:testDebugUnitTest :app:assembleDebug # BUILD SUCCESSFUL, 154 tests, 0 failures ``` New coverage: - `HttpMediaActionsApiTest` — MockWebServer contract tests for the five endpoints: paths, bearer headers, the `metadataClass`/`value` body, `204`-empty for trash/restore, `403 → ForbiddenApiException`, `401 → UnauthorizedApiException`. - `MediaViewerViewModelTest` — detail load (once, seeding favorite + absolute URLs, non-blocking), optimistic favorite while in flight, unfavorite-via-DELETE, the first-tap fetches-first regression guard, favorite failure → revert + working retry, forbidden → owner-only, trash/restore event flow, trash retry, download progress + bearer token + failure + no-preview, share link, filename, plus the share flow (photo staged → `ShareReady`, staging failure → link fallback, video → link without staging, no-preview → link, no-link + no-preview → nothing, missing session → re-login, in-flight debounce). - `ShareTargetTest` — the pure share-target decision: photo → file, unknown type → photo, video → link with or without a rendition, blank preview → link, photo can still stage without a known link, `Nothing` when neither is available, and web-link normalisation. - `TimelineViewModelTest` — `removeItem` shifts the following item into place, ignores unknown ids, does not stall `load-more`. - `ViewerDateTest` — duration formatting and its null/zero/negative cases. All user-visible strings are in `values/` (German), `values-en/`, `values-da/`; keys and format placeholders verified consistent across the three locales. ## Risks - **Trashing the only loaded item** briefly leaves a black screen with just the Undo snackbar. Correct by design, but it is a state we only reach with a one-photo album — worth a manual look. - **Share target** is now the file itself (see "Decisions"). The link path survives only as fallback, so reverting to link-only sharing is a one-line change in `decideShareTarget`. Note the wording when a *photo* fails to stage says the link was shared while the photo could not be prepared — accurate, but the recipient then gets a link rather than the picture. - **`ShareIntent.Nothing` reuses `viewer_no_preview_save`.** Reachable only when there is no session link *and* no rendition (effectively logged out), and its wording says "save" rather than "share". Cosmetic and near-unreachable; a dedicated string would fix it if anyone minds. - **Two snackbars can queue.** The event loop is deliberately sequential (one message at a time reads calmer than stacked toasts), so a message raised while the Undo snackbar is still on screen waits for it. The Undo window is `Long`, so that wait can be a few seconds. - **Device-local download naming** is `memories-{mediaItemId}.jpg`, which is stable and collision-free but not human-readable. Deliberate: it avoids guessing at a title the server may not have. ## Follow-up commit: share the photo file Second commit on this branch, addressing the share-target risk above. - `media/MediaShareCache.kt` + `media/AndroidShareCache.kt` — stages a rendition into `cacheDir/share/` via `.part`-then-rename, so no partially written file is ever handed out. - `media/RenditionHttp.kt` — the HTTP rendition fetch factored out of `AndroidMediaDownloader` and shared by save and share, so the two paths cannot drift. - `ui/timeline/ShareTarget.kt` — `decideShareTarget()` / `shareWebLink()` / `shareFileName()`, the testable decision. - `res/xml/file_paths.xml` + a `FileProvider` entry in `AndroidManifest.xml` exposing only `cache-path "share"`. - `MediaViewerViewModel` — `sharing` / `preparing` state, `ShareReady` and `ShareLink` events; `shareText` now delegates to `shareWebLink`. - `MediaViewerScreen` — the progress pill reads `downloads ?: preparing` and labels itself accordingly (the save icon no longer shows busy while a share is preparing), `shareFile()` builds the `ACTION_SEND`, and `startChooser()` is shared with the text path. - Strings `viewer_share_preparing` / `viewer_share_video_link` / `viewer_share_link_fallback` in de, en and da. Verification for this commit: `./gradlew :app:testDebugUnitTest :app:assembleDebug` — BUILD SUCCESSFUL, **154 tests, 0 failures**, APK assembled. CI on the PR: *Android unit tests and debug APK* success, *Run scoped PR tests* success, non-Android scopes correctly skipped. Not merged — left for orchestrator review.
Extend MemoriesApi/HttpMemoriesApi with the endpoints the Phase 1 viewer
needs: GET /api/media/{id}, POST/DELETE /api/media/{id}/metadata-overrides
for the favorite toggle, and POST /api/media/{id}/trash plus /restore.

Implemented against observed server behaviour rather than the OpenAPI
document: the controller is annotated @ResponseStatus(NO_CONTENT), so
trash/restore answer 204 with an empty body while the spec claims
200 + MediaDetail. executeEmpty() accepts any 2xx and ignores the body,
which matches what the web client already does.

Adds ForbiddenApiException, mapped from 403, so the screen can say
"only the owner can do this" instead of showing a generic failure.
feat(android): Phase 1 viewer actions — favorite, share, download, trash, info sheet
All checks were successful
Wiki Sync / Sync wiki from docs (push) Has been skipped
Build and Deploy / Detect changed services and test scopes (push) Successful in 3s
Build and Deploy / Smoke API and media worker (push) Has been skipped
Build and Deploy / Smoke web (push) Has been skipped
Build and Deploy / Smoke ML worker (push) Has been skipped
Build and Deploy / Smoke people worker (push) Has been skipped
Build and Deploy / Build postgres image (push) Has been skipped
Build and Deploy / Build plants worker image (push) Has been skipped
Build and Deploy / Build converter worker image (push) Has been skipped
Build and Deploy / Deploy postgres (push) Has been skipped
Build and Deploy / Build API image (push) Has been skipped
Build and Deploy / Build media worker image (push) Has been skipped
Build and Deploy / Build ML worker image (push) Has been skipped
Build and Deploy / Build people worker image (push) Has been skipped
Build and Deploy / Build web image (push) Has been skipped
Build and Deploy / Deploy API (push) Has been skipped
Build and Deploy / Deploy web (push) Has been skipped
Build and Deploy / Deploy media worker (push) Has been skipped
Build and Deploy / Deploy ML worker (push) Has been skipped
Build and Deploy / Deploy plants worker (push) Has been skipped
Build and Deploy / Deploy people worker (push) Has been skipped
Build and Deploy / Deploy converter worker (push) Has been skipped
Build and Deploy / Clean Docker build artifacts (push) Has been skipped
Build and Deploy / Run scoped PR tests (push) Successful in 4s
Build and Deploy / Android unit tests and debug APK (push) Successful in 2m51s
2fae27b63a
Adds a second row to the viewer chrome (favorite, share, save, details,
trash) directly under the existing top bar with the same 80% black scrim,
so both rows read as one block. A bottom bar was ruled out because it
would overlap the video controls row.

Favorite flips optimistically and reverts with a Retry snackbar action if
the server disagrees; tapping the heart before the item's detail has ever
loaded fetches it first rather than guessing, so the first tap on an
already-favorited photo actually does something.

Share hands the system share sheet the web media page
({serverUrl}/media/{id}) rather than previewUrl, which sits behind bearer
auth and would open a login wall for the recipient.

Download saves the preview rendition into Pictures/Memories through
MediaStore (minSdk 29, so no runtime permission), with an IS_PENDING guard
so a failed write never leaves a half-written row. Progress shows as a
pill stacked under the snackbar; both live outside the chrome so a save
outlives a chrome hide. The original file cannot be saved — there is no
user-facing /original endpoint (see ISSUE-115) — so only the preview is
ever offered and the control disappears when previewUrl is absent.

Trash asks for confirmation in plain language first, then POSTs, shows
"Zum Papierkorb verschoben" with an Undo action that restores, and drops
the item from the pager so the next photo takes its place. If that empties
the list, the screen holds on the empty state until Undo resolves instead
of navigating away with the snackbar still up.

The info bottom sheet renders only fields the payload actually carries —
capture date, duration, title, description, things — never placeholders,
never raw JSON, never internal field names. MediaDetail has no persons
field, so people are simply not offered (ISSUE-117).

MediaViewerViewModel holds no Context: it emits typed events and messages
that the screen resolves against resources, which keeps it JVM-testable.
MemoriesApp.kt changes are four lines (one import, one viewModel(), two
parameters) to stay clear of the concurrent nav-shell lane.
feat(android): share the photo file instead of a link
All checks were successful
Wiki Sync / Sync wiki from docs (push) Has been skipped
Build and Deploy / Detect changed services and test scopes (push) Successful in 2s
Build and Deploy / Smoke API and media worker (push) Has been skipped
Build and Deploy / Smoke web (push) Has been skipped
Build and Deploy / Smoke ML worker (push) Has been skipped
Build and Deploy / Smoke people worker (push) Has been skipped
Build and Deploy / Build postgres image (push) Has been skipped
Build and Deploy / Build plants worker image (push) Has been skipped
Build and Deploy / Build converter worker image (push) Has been skipped
Build and Deploy / Deploy postgres (push) Has been skipped
Build and Deploy / Build API image (push) Has been skipped
Build and Deploy / Build media worker image (push) Has been skipped
Build and Deploy / Build ML worker image (push) Has been skipped
Build and Deploy / Build people worker image (push) Has been skipped
Build and Deploy / Build web image (push) Has been skipped
Build and Deploy / Deploy API (push) Has been skipped
Build and Deploy / Deploy web (push) Has been skipped
Build and Deploy / Deploy media worker (push) Has been skipped
Build and Deploy / Deploy ML worker (push) Has been skipped
Build and Deploy / Deploy plants worker (push) Has been skipped
Build and Deploy / Deploy people worker (push) Has been skipped
Build and Deploy / Deploy converter worker (push) Has been skipped
Build and Deploy / Clean Docker build artifacts (push) Has been skipped
Build and Deploy / Run scoped PR tests (push) Successful in 5s
Build and Deploy / Android unit tests and debug APK (push) Successful in 2m57s
554d55e54a
Recipients may have no account and no route to the server, so the share
sheet now hands them the actual picture — standard family UX, like Google
Photos.

- Stage the preview rendition into cacheDir/share and pass it to
  ACTION_SEND through a FileProvider (${applicationId}.share) with
  FLAG_GRANT_READ_URI_PERMISSION. Bytes land under a .part name and are
  renamed into place, so a racing tap can never hand over a truncated
  JPEG, and only that one subdirectory is exposed to foreign apps.
- Videos keep URL-text sharing: no video rendition exists yet (ISSUE-115),
  so the sender is told recipients must be signed in.
- A photo that fails to stage, or a FileProvider path that is refused,
  falls back to the same web link with a note — a share tap is never a
  dead end.
- Extract the photo/video/failure decision into decideShareTarget(), a
  pure function free of Android types, so it is unit-testable.
- Factor the HTTP rendition fetch into one helper shared by the MediaStore
  save and the cache staging, so the two paths cannot drift apart.

Strings added in de (default), en and da.

Verification: ./gradlew :app:testDebugUnitTest :app:assembleDebug —
154 tests, 0 failures, APK assembled.
chris merged commit fbe65a1aa7 into main 2026-10-11 16:59:26 +02:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
chris/memories!1116
No description provided.