Pulse Notes · v0.6.4 release Latest v0.6.4 · versionCode 14

Side-load v0.6.4
if your UpdateChecker is still on v0.6.3.

v0.6.4 ships the in-app UpdateChecker and the manifest URL fallback chain. v0.6.3 users cannot auto-update because the v0.6.3 APK has a single manifest URL baked in at build time — and that URL was retired in the same deploy that published v0.6.4. This page is the manual side-load path.

Why this page exists

The v0.6.3 build cannot see v0.6.4.

The Pulse Notes in-app updater polls a remote manifest at a URL that was compiled into the APK at build time. v0.6.3 was built before the manifest URL fallback chain existed, so it polls a single host. That host was retired when v0.6.4 deployed, and v0.6.3 cannot reach the new host. Side-loading v0.6.4 installs the new build with the new fallback chain, and from then on every future release will reach the device through the in-app updater.

  1. v0.6.3 polls a single host

    The v0.6.3 APK was built with DEFAULT_MANIFEST_URL = https://hrkbksh0x0xz4.space.minimax.io/updates/android.json in pulse-android/web/src/lib/update-checker/update-checker.ts. No chain. No fallback. The updater polls that one host and trusts whatever it returns.

  2. v0.6.4 retired that host

    v0.6.4's manifest lives on a different host. The R87 host still serves a v0.6.2 manifest (it was never updated to v0.6.3). v0.6.3 polls the R87 host, gets v0.6.2 back, and shows "your version is up to date" — even though v0.6.4 has been live for hours.

  3. v0.6.4 adds the chain

    v0.6.4 ships DEFAULT_MANIFEST_URLS as an array of 5 known hosts (most-recent first), with the VITE_UPDATE_MANIFEST_URL env override at the head. From v0.6.4 onward, every APK that ships after a host rotation will still find a valid manifest through the chain.

  4. Long-term fix: a stable host

    The fallback chain is a bridge, not a permanent solution. The architectural fix is to publish the manifest at a stable URL that does not rotate — Cloudflare R2 bucket, GitHub Pages on TimesNuRoman/pulse, or raw GitHub at raw.githubusercontent.com/TimesNuRoman/pulse/main/updates/android.json. Tracked as an R93+ follow-up; this page is the bridge for v0.6.3 users today.

Side-load v0.6.4 · Android · universal APK

Install v0.6.4 manually.

4.35 MB APK · no Google Play · no account · no telemetry.

Download APK ↓ 4.35 MB Read the changelog
  1. 1

    Open the APK in a browser

    On the Android device, open https://9u26sgn3vblim.space.minimax.io/downloads/pulse-notes-0.6.4-debug.apk in Chrome (or any browser). Confirm the download. Some browsers may show a warning for downloads outside Google Play — that is expected.

  2. 2

    Allow installs from this source

    Android will ask for permission to install from the browser (or file manager). Tap Settings, toggle Allow from this source, then return and tap Install. This permission is per-app and can be revoked after the install.

  3. 3

    Verify SHA-256 (optional)

    Power users can verify the download against the published fingerprint. The expected SHA-256 is: 

    FB6FD8A0C720DF7FB4CC902FC480EFF258A5AD5D7B5FF7A24893BA1437A0C58E

    Short form: FB6FD8A0…0C58E.

  4. 4

    Open Pulse Notes v0.6.4

    The installer replaces the existing Pulse Notes app (same appId, app.pulse.notes) and preserves the local SQLite database. All notes, tags, and backlinks are intact. The in-app UpdateChecker is now active and will handle every future release.

versionName 0.6.4
versionCode 14
appId app.pulse.notes
minSdk · targetSdk 24 · 36
SHA-256 FB6FD8A0…0C58E

Full v0.6.4 release notes →