Skip to content

ZenNotes for Android 1.1.55: Cloud linking no longer stops on the Welcome note

Latest

Choose a tag to compare

@adibhanna adibhanna released this 03 Nov 22:18
85c8e20

Version 1.1.55, versionCode 58, November 3, 2026, following 1.1.54 (57). PR #148 carries e282375; the signed bundle zennotes-1.1.55-vc58.aab (40,099,943 bytes, SHA-256 ccb32e4a53d6d94574d4f82fe3f4360386ef13149a30e19a4f8da5571e84b03f) is built from 67ed732, merged as 85c8e20 with the same tree.

What changes on the phone

  • Linking to a Cloud vault no longer stops on the Welcome note. A fresh install writes its own Welcome note. When the Cloud vault already held a different copy, the first sync called that a conflict and paused for the file. Now an untouched Welcome note yields: the phone takes the Cloud's copy, or uploads its own when the Cloud has none. A note you edited still asks which version to keep, so your words are never replaced.

Under the hood

The core is unchanged from 1.1.54: core-2.82.0-core.h7fbea7b1c6714eb0. The fix is in this app's own Cloud bridge: src/bridge/welcome-note.ts recognizes the untouched seed by hash, cloud-sync-repository.ts holds it back on the first sync, and mobile-cloud-sync.ts says when a sync is the first one.

Validation

  • npm test: 514 tests, 514 passed, on 67ed732, with new unit and integration cases for this fix in cloud-sync-repository.test.ts and mobile-cloud-sync.integration.test.ts.
  • CI on #148: the build job and the emulator launch job passed (run 41725047430).
  • Not walked on Android against a real Cloud account: the fix is proven by the tests above, not by a device run of this case.

Play Console submission

1.1.54 (57) is live. Production, Create new release: the AAB, processed as 58 (1.1.55), no devices lost, full rollout, and sent for review on November 3, 2026. Play Console reads Changes in review.

This release carries Play's signed universal APK from App bundle explorer as zennotes-1.1.55-universal.apk: 40,367,596 bytes, SHA-256 e3703ccdf24252e418b7e0c3d0517fd9ed5765cc4a3e8dc2616d8500ca428717, md.zennotes 58 / 1.1.55, min 24 / target 36, signer 9f1af3a4..., Play's app-signing key, no CHECK_LICENSE, no pairip.

How to test locally

  1. npm ci && npm run build && npx cap sync android, then open android/ in Android Studio and run on a device or emulator.
  2. Use a ZenNotes Cloud vault that already holds a Welcome note written by an older version of the app.
  3. Fresh install, then link this device to that vault. Before: sync pauses on a conflict over the Welcome note. After: it finishes with no conflict, and the Welcome note is the Cloud's copy.
  4. Fresh install again, edit the Welcome note first, then link. It still asks which version to keep.