Skip to content

ZenNotes for Android 1.1.32: folder files, steady Edit scrolling and Kanban by due date

Choose a tag to compare

@adibhanna adibhanna released this 05 Oct 23:07
· 18 commits to main since this release
ce3a448

ZenNotes for Android 1.1.32: folder files, steady Edit scrolling and Kanban by due date

Version 1.1.32, versionCode 35, October 5, 2026, following 1.1.31 (34). PR #97 carries beb0408; the signed bundle zennotes-1.1.32-vc35.aab (31,572,679 bytes, SHA-256 16625015…47f99c) was built from that commit.

What changes on the phone

  • Browse lists a folder's files as well as its notes: pictures, PDFs and other attachments appear after the notes (#95, with core 2.62.0).
  • Scrolling a note in Edit mode stays where you scroll instead of jumping back to the cursor while the keyboard is up (ZenNotes/zennotes#891, #96).
  • A note keeps its creation date when it is renamed or moved (#95).
  • A file that has not reached this device says so in the note instead of drawing an empty player, and turns into the picture or player when it arrives.
  • Kanban columns can be ordered by due date: Order, next to Group by (ZenNotes/zennotes#889).
  • Cloud: Settings → Cloud opens on what needs you and says why an automatic backup was skipped and which plan limit a backup hit; a restored note leaves no copy behind; a restore that only changes a note's capitalization renames it in place, and a run stopped between its two renames recovers.
  • Fixed: a dated link such as [[2024.01.15]] opens its note instead of a browser address.

Under the hood

Core core-2.62.0-core.hcf81934394c63533 was built by CI from ZenNotes/zennotes fb3d13f8, the v2.62.0 release commit (run 37378093758), and published as a pre-release; iPhone 1.18.0 vendors the identical archives. core:adopt checked SHA-256, SHA-512, packed versions and clean-source provenance, and the lockfile diff is only the three @zennotes pins.

Source: branch release/1.1.32 from main 8559c57 (the merges of #95 and #96): adoption 98f0ffc, version commit beb0408 (Gradle, the bridge fallback version, package.json and the lockfile root). No native code, permission or SDK changes.

Validation

  • On core 2.62.0: boundaries, typecheck and 229 JavaScript tests passed, plus the Vite build and Capacitor sync. JDK 21 bundleRelease passed.
  • PR #97 CI on beb0408 passed: the build job and the emulator launch job (18m39s).
  • The folder file rows, the missing-file notice, the dated link and Kanban Order were checked on the iPhone build of the same core on a simulator; not on an Android device here.

Play Console submission

1.1.31 (34) was live. Production, Create new release: release notes (476 characters, inside <en-US> tags), the AAB dropped in by Adib, processed as 35 (1.1.32): API 24+, target SDK 36; no devices lost (12,320 phones, 6,749 tablets); 3 MB update; only the usual "no deobfuscation file" warning. Saved, "Submit 1 change for review", "Send changes for review"; Google published it the same evening. Managed publishing is off.

PR #97 merged as ce3a4484 (merge tree equals beb0408, the AAB's source); lightweight tag v1.1.32. This release carries Play's signed universal APK from App bundle explorer as zennotes-1.1.32-universal.apk: 31,826,753 bytes, SHA-256 e3f20ca1…a490, md.zennotes 35 / 1.1.32, min 24 / target 36, signer 9f1af3a4… as since 1.1.22, no CHECK_LICENSE or 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. Put a picture in a note folder, open Browse on that folder: the picture is listed after the notes. Open Tasks → Kanban and set Order to Due date: each column sorts by date.