Repository navigation
ZenNotes for Android 1.1.21: file operations that finish or roll back
ZenNotes for Android 1.1.21: file operations that finish or roll back
File operations now either complete or restore the original state, folder vaults tell a missing file from a broken connection, and a Cloud vault deleted on the server unlinks itself without touching your notes. The app installs the published ZenNotes core packages instead of compiling desktop source, and adopts app core 2.51.0.
What changes on the phone
- Rename, move, trash, and Empty Trash finish completely or roll back. A note and its comment sidecar move together; if the second step fails, the first is put back and the failure is reported. Renaming a folder restores its icon and color settings if the metadata write fails.
- Renaming or moving a vault saves pending edits first and reopens cleanly. A failed reopen moves the folder back. Swipes, long-press menus, Kanban drags, and attachment pickers started before a vault switch are ignored afterward.
- Folder vaults report real errors. For vaults opened through Android's folder picker, a file that truly does not exist is distinguished from revoked access, an empty provider response, or an unreadable document. Those surface as errors instead of being treated as missing files.
- A Cloud vault deleted on the server unlinks itself. The phone removes only that link and its sync state, archives the old state locally (including unsent conflict drafts), and leaves your notes and other linked vaults untouched. Offline, sign-in, permission, and server errors never unlink anything.
- Shared editor fixes from app core 2.50.1 to 2.51.0. Wikilink picker stays closed for
[[inside code;{{modified_date}}tokens follow the last save; renaming or moving an attachment rewrites the notes that reference it; forwarded and cancelled tasks stay off Kanban boards; tapping an image in the reading view opens its asset menu; daily-note rollover carries the real open tasks. - Confirmations use the shared wording. Delete asks to move the note to Trash, like desktop; rename, move, and archive prompts use the same dialogs.
Under the hood
The shell installs @zennotes/app-core, @zennotes/bridge-contract, and @zennotes/shared-domain as immutable archives whose version, checksum, and source commit are recorded in vendor/zennotes/manifest.json, and uses only their public entry points; a boundary check verifies the checksums, a single React/CodeMirror copy, and that no import reaches a private core path. The bridge identifies itself as platform android with hostKind: 'android'. Storage Access Framework reads return distinct codes for missing files, directories, revoked access, and provider failures, covered by an instrumentation fixture.
Core packages: core-2.51.0-core.h49d73b531d346192, built from desktop commit 8ff2cb86 (tag v2.51.0), replacing the 2.50.0 source pin 104416f5. Capacitor 8.5.2, CodeMirror view 6.43.11 and state 6.7.4, Vite 8.3.0.
Installing the APK
zennotes-1.1.21-universal.apk is the Google Play-signed universal APK for version 1.1.21 (24), Android 7.0 and later, same certificate as before, attached exactly as downloaded from Play Console. If a sideloaded upgrade opens to a Google Play requirement, install through Google Play. Sideloaded installs do not self-update; use Obtainium.
Validation: 149 automated tests, boundary check, typecheck, production build, native unit tests, lint, and debug build passed. Android 15 emulator: onboarding, vault creation, keyboard-toolbar editing, autosave, Delete with confirmation, Browse, cold relaunch, and reinstall over existing data passed; rename with comments, trash, restore, Empty Trash, and permanent delete verified byte-exact on the device filesystem. Cloud-vault deletion was adapter-tested only. All 469 app assets in this Play-signed APK match the submitted bundle.