Skip to content

ZenNotes for Android 1.1.13

Choose a tag to compare

@adibhanna adibhanna released this 31 Aug 16:43
94610d7

ZenNotes for Android 1.1.13: the attach button, fixed

1.1.12 added a paperclip to the keyboard toolbar. This release fixes the
three things that were wrong with it — one per vault kind, plus a crash.

Attachments land where they belong

  • Local vaults: files went to the vault root. The import asked for a
    unique name in '' — the vault root — wrote the file there, and hand-built
    the link as ../ repeated per folder depth, so a note in a subfolder got
    ![name](<../name.jpg>) and rendered as a broken image. Paste already
    wrote to assets/, and so did the cloud vault, which is why attach and
    paste behaved like two different features.

    Attached files now go to assets/ and are linked by vault-relative path —
    an image as ![[assets/pic.jpg]] — matching paste and the cloud vault.
    Reported on Discord by xenin, whose shape_image 18.jpg was the
    seventeenth name collision in their vault root.

  • Self-hosted vaults: every upload arrived corrupt (#40). The upload
    hand-built its multipart body as a single string and marked the file part
    Content-Transfer-Encoding: base64. That header is a MIME construct —
    RFC 7578 dropped it from multipart/form-data, and Go's mime/multipart
    ignores it — so the server wrote the base64 text to disk as the file's
    bytes. The attachment landed with the right name, about a third larger
    than the original, and unreadable by anything.

    The bytes have to stay base64 to cross the native bridge, so the upload
    now uses Capacitor's supported dataType: 'formData' route, where the
    native layer decodes the entry and writes raw bytes into the part.
    Verified against a running Go server: the stored file is now byte-identical
    to the original (478,762 bytes, \x89PNG) instead of 4/3 its size.

  • Imported filenames are sanitized before they hit the filesystem.

An unreadable attachment no longer kills the app

The only crash cluster in 1.1.11's Android vitals: Capacitor's
WebViewLocalServer let a document provider's IllegalArgumentException
escape shouldInterceptRequest while serving a content:// attachment from
a folder (SAF) vault, taking the process with it. MainActivity now wraps
that call — any RuntimeException while resolving a request answers 404, so
a stale or unreadable attachment is a broken image, not a dead app.

Under the hood

The attach file input is now positioned off-screen rather than
display:none, matching the iOS shell (WebKit won't present a picker for a
hidden input; Android's WebView accepts either). Build and CI dependency
bumps: Gradle wrapper 8.14.5, actions/checkout 7, actions/setup-node 7,
actions/setup-java 6, com.google.gms:google-services 4.5.0, and a
Dependabot config that keeps KaTeX inside the app core's ^0.16 range.

Same app core as 1.1.12 (2.38.0, pinned to upstream 43994ff) — this is a
shell-only fix release.

Files already sitting in a vault root do not move themselves, and
attachments already uploaded corrupt stay corrupt and need re-adding.

Installing the APK

  • zennotes-1.1.13-universal.apk is 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.