meshbay.git/packages/meshbay-hub/tests/test_photo_sync_ui.py, branch 0.20

feat(android): no text messages backup, and one build again

2026-10-15T13:09:58Z

READ_SMS sits behind restricted settings outside a store and Play keeps it for the default SMS application: not worth a second build. Co-Authored-By: Claude Opus 5.5

feat(android): back up WhatsApp's own chat backups, and its media if asked

2026-10-10T14:29:20Z

A WhatsApp section takes WhatsApp's folder through the picker, sends its encrypted Databases and Backups (not the dated copies of earlier weeks) into /-whatsapp, and names the restore set in the manifest. Co-Authored-By: Claude Opus 5.5

feat(android): back up the files of folders the person chooses

2026-10-10T13:50:39Z

A Files section takes folders through the system picker (no storage permission), refuses DCIM, Pictures and Movies, skips what the photo backup sends, and runs on the photo backup's own runner into /-drive. Co-Authored-By: Claude Opus 5.5

feat(android): back the videos of the chosen albums up beside the photos

2026-10-10T13:11:52Z

A 'Videos too' option, off by default, sends them into the same YYYY/YYYY-MM folders. Files are read from the phone a ranged chunk at a time, so a large video is never whole in the page. Co-Authored-By: Claude Opus 5.5

feat(android): back the calendars up as an iCalendar file

2026-10-10T12:52:57Z

A Calendar section sends every calendar the person can edit, as a dated .ics, into /-calendar once a day when it changed. Co-Authored-By: Claude Opus 5.5

feat(android): back text messages up, in a build Play does not get

2026-10-10T12:40:05Z

A Messages section sends the SMS added since the last copy, as restorable XML, into /-messages/YYYY. A play flavor has neither READ_SMS nor the code that reads messages; full is the default. Co-Authored-By: Claude Opus 5.5

feat(android): one backup destination, a group the account owns alone

2026-10-10T12:21:46Z

Chosen once at the top of Android Sync for every kind; photos and contacts go into /-photos and -contacts. Owner and sole member are checked at set-up and before every run. Co-Authored-By: Claude Opus 5.5

feat(hub): photo backup moves to its own Android Sync page

2026-10-10T10:35:15Z

A Phone section of the side menu leads to it, on the Android application only; Settings no longer holds it. Co-Authored-By: Claude Opus 5.5

feat: back up the phone's photos to a group, once a day on Wi-Fi

2026-10-09T16:23:56Z

The Android application sends the photos taken on the phone to one folder of one group chosen by the member (docs/MESHBAY_DESIGN.md §9.12). The phone lists MediaStore, keeps a ledger of what was sent and hands each photo's bytes to the page by an opaque token on the packaged origin; the page decides when a run is due and uploads through the existing path, one photo at a time under a slot. - Once a day from the last finished run, on an unmetered network only; "Back up now" asks first on mobile data. Leaving Wi-Fi stops after the file in flight. - Photos already on the phone are sent by default, newest first, under /YYYY/MM; edits are sent beside the original as -edited-. - Additive by construction: nothing is ever deleted, renamed or replaced on the node, and a photo deleted on the node is not sent again. - A confirmation names the group, owner, members, folder and size when the destination or starting point changes; a lasting refusal (disk full, folder read-only or gone, no longer a member) is said once and retried a day later. - No ACCESS_MEDIA_LOCATION, so the platform redacts photo locations. - A dataSync foreground service keeps a run going with the screen off. HEIC/HEIF photos are sent but not shown in Photos yet (§15.2). Co-Authored-By: Claude Opus 5.5