Repository navigation
ZenNotes for Android 1.1.15
ZenNotes for Android 1.1.15: Cloud conflicts become clear choices
The app core moves from 2.38 to 2.44, and with it the phone gets the same
conflict resolver as desktop: safe edits merge on their own, a real overlap
asks one question, and sync stops leaving surprise (cloud conflict) notes
in your vault.
Review sync changes where you already work
Two devices editing the same note between syncs used to end in a numbered
conflict copy. ZenNotes/zennotes#683 (reported by @uNyanda) asked for
better; 2.44.0 delivers it, on Android too.
- Safe edits merge automatically, three-way against the last synced
version, without interrupting you. - Only the ambiguous part needs a decision. A 1 file needs review ·
Review now prompt appears in the editor's status bar, and the same
queue lives in Settings → Cloud. The resolver labels This device,
Other device, and Last synced, shows the suggested combined note,
and asks which wording to keep for each overlap. Edit the combined note
directly, or keep one complete version instead. - An honest first-sync choice. With no earlier shared version, ZenNotes
shows both complete notes, says why it can't know which is newer, and
offers to keep either, both, or combine them yourself. - Finish later without losing progress. Leaving a note unresolved asks
for confirmation; the Cloud version, the last-synced version, and your
draft wait in private app storage while unrelated notes keep syncing. - No vault or task pollution. New conflicts never become numbered files,
and a waiting note's tasks stay out of Tasks, Calendar, and Kanban until
it's resolved. - Every file type, checked twice. Text, binary, delete, move, and name
collisions share one queue, and both sides are re-verified before a
decision is saved.
Six app-core releases in one update
The build now carries 2.39 through 2.44; the fixes that apply on a phone:
- Sync incomplete says which files, and why, with an Open button, and
catching up on a note another device saved several times no longer
produces a conflict copy. - Every device links attachments the same way (ZenNotes/zennotes#699),
the app-core half of the attach fixes 1.1.13 shipped on the shell side. - Editor: the wikilink picker keeps a link's section and alias (#686),
the marker hop steps over auto-paired quotes (#685), Auto-close Markdown
keeps its hands off code (#718), a trashed note's bin icon deletes for
good (#712), and a pasted video no longer takes the keyboard away.
Harper stays on the desk
2.44.0 adds Harper, an on-device grammar checker, to desktop and web (off
by default). Phones rely on the system keyboard for spelling, so the
Android build stubs Harper and its 15.6 MB binary out: the app doesn't grow.
It does keep what you taught Harper elsewhere — the vault dictionary and
ignored suggestions survive a settings save from this device, so a sync
from the phone no longer erases them.
Under the hood
The mobile bridge gains the five conflict operations desktop and iOS use,
routed through the shared sync coordinator. Toolchain: Vite 8.2 and the
React plugin 6.1, plus an npm override for an audited transitive
dependency. Native side unchanged: Capacitor 8.5, SDK 36, minSdk 24.
Pinned to upstream f156bb1 (the final 2.44.0 tag). Ships alongside ZenNotes
for iOS 1.9.6, so the two shells stay in step.
Installing the APK
zennotes-1.1.15-universal.apkis a universal build for all supported
devices (Android 7.0+). Download it on your device, open it, and allow the
install when Android asks.- It carries the same signature as the Google Play build, so you can
switch between Play and GitHub installs without uninstalling (your notes
stay put either way). - Sideloaded installs don't self-update — watch this repo's Releases, or
point Obtainium at it for
automatic update notifications.