Side-load v0.6.5
if your UpdateChecker is stuck on v0.6.3 or v0.6.4.
v0.6.5 is the R93 bridge release. The manifest URL chain grows from 5 to 7 hosts (R92 and R90 are added at the head), so v0.6.5+ devices can auto-update forward even if older hosts go down. v0.6.3 and v0.6.4 users cannot auto-update because their baked-in chain does not include the new hosts — side-load v0.6.5 from this page.
The v0.6.3 and v0.6.4 builds cannot see v0.6.5.
v0.6.3 was built with a single manifest URL baked in at
build time. v0.6.4 was the first release with the fallback
chain (5 hosts, most-recent first), but that chain is now
incomplete: it predates the R92 site
(yv5eeknt6h6sa.space.minimax.io) and the R90
canonical site (ad67rp710vsl7.space.minimax.io).
v0.6.3 polls the R87 host, gets v0.6.2 back, and shows "your
version is up to date". v0.6.4 polls the R88 / R87 hosts,
gets v0.6.2 / v0.6.3 back, and shows the same message. v0.6.5
adds the missing two hosts at the head of the chain and ships
a new APK. Side-load v0.6.5 to install the chain, then every
future release will reach the device through the in-app
updater.
-
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.jsoninpulse-android/web/src/lib/update-checker/update-checker.ts. No chain. No fallback. The updater polls that one host and trusts whatever it returns — which is v0.6.2, not v0.6.5. -
v0.6.4 has a 5-host chain — but it's stale
v0.6.4 shipped the first multi-host chain (R88, R87, R85, R81, R78). R92 and R90 are not in that chain because the R92 site (
yv5eeknt6h6sa.space.minimax.io) and the R90 canonical site (ad67rp710vsl7.space.minimax.io) were deployed after the v0.6.4 APK was built. v0.6.4 still finds a valid manifest (one of the older hosts still returns v0.6.2 or v0.6.3), so the UpdateChecker shows "your version is up to date" — even though v0.6.5 is live. -
v0.6.5 grows the chain to 7
v0.6.5 adds two hosts at the head of the chain: R92 (
yv5eeknt6h6sa) and R90 (ad67rp710vsl7). The chain is now[R92, R90, R88, R87, R85, R81, R78]— most recent first. Every v0.6.5+ APK that ships after a host rotation will still find a valid manifest through the chain. TheVITE_UPDATE_MANIFEST_URLenv override is still supported and goes at index 0 if set. -
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 atraw.githubusercontent.com/TimesNuRoman/pulse/main/updates/android.json. Tracked as an R94+ follow-up; this page is the bridge for v0.6.3 and v0.6.4 users today.
Install v0.6.5 manually.
4.39 MB APK · no Google Play · no account · no telemetry.
- 1
Open the APK in a browser
On the Android device, open
https://uiwb7l19o4r7b.space.minimax.io/downloads/pulse-notes-0.6.5-debug.apkin Chrome (or any browser). Confirm the download. Some browsers may show a warning for downloads outside Google Play — that is expected. - 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
Verify SHA-256 (optional)
Power users can verify the download against the published fingerprint. The expected SHA-256 is:
AD81D03C87BB96C121299F8843F1E25596FF7AE657D750D27D7A4C351D1D7607Short form:
AD81D03C…1D7607. - 4
Open Pulse Notes v0.6.5
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 with the 7-host chain and will handle every future release.