Skip to content

CallPages Merchant v1.4.1

Choose a tag to compare

@vasilyespana vasilyespana released this 11 Oct 00:02
· 8 commits to main since this release
2b5fcbc

CallPages Merchant v1.4.1 — canonical Google sign-in fix

Production release of the Google sign-in repair (monorepo PRs #201 + #208, shipped to master via release PR #209, merge commit c4a910ec6a47f9edd8abcf1a81ee5c76982a057c).

App version: 1.4.1 — arm64 versionCode 62, armeabi-v7a versionCode 61. Both sit above every fielded build (v1.4 = 52; the broken test builds = 42), which also eliminates the version-downgrade install rejection diagnosed behind the "package not valid" reports — Android refuses to install a lower versionCode over a higher one, and several installers surface exactly that as "package not valid."

What was fixed

Google sign-in (worker — the deterministic defects):

  • mobile_auth_codes migration reordered: the login_id column is added before its index, with per-statement failure isolation — the old order aborted the migration on pre-existing tables, so sign-in codes could never be minted (proven live against the production schema).
  • GET /api/v1/auth/mobile-status no longer consumes ("burns") the one-time code when the app polls it; the code is claimed atomically at exchange (UPDATE … WHERE used=0, exactly-one-row check). Previously the polling path burned the code and the subsequent exchange always failed — sign-in could not complete after choosing an account.
  • Regression suite T1–T6 (src/mobile-auth.test.js) written failing-first, then fixed; full worker suite 167/167.

Android app:

  • Every Credential Manager failure path now logs the concrete exception type (no tokens/secrets logged) and surfaces it in failure messages, instead of one generic "sign in could not be completed."
  • The Custom Tab polling path logs server errors instead of silently polling for ~5 minutes.
  • Pre-existing staging compile break repaired (a merge artifact left a call to a non-existent method); dead WebView-login remnants removed.

Architecture (unchanged, now working as designed): Credential Manager (Sign in with Google) is the primary path — Google's canonical account picker over the accounts already on the device. Chrome Custom Tab + verified App Link + login_id polling remains the fallback for accounts signed in only in the browser.

Verification (MVR-VP)

  • Install + launch SUCCESS on two physical cloud devices: Google Pixel 7 and Samsung Galaxy S23 (device-gate run 38095170000).
  • Full-flow E2E on a real Pixel 7 (BrowserStack Espresso, run 38094177915): launch & auth → FTUE onboarding → native first-page creation for a zero-pages account → navigate/edit — all four stages passed, including session state carrying into the web dashboard with no login kick-out.
  • Live staging exercise of the fixed endpoints: poll → poll (same code) → exchange (consumed) → second exchange → 401, exactly as specified.
  • Production post-merge checks: GET /api/health → 200 ok:true; GET /api/auth/google → 302 to Google (production OAuth is configured).

Screenshots — app launch on real devices

Google Pixel 7

Launch — Pixel 7

Samsung Galaxy S23

Launch — Galaxy S23

APK checksums (SHA-256)

  • arm64-v8a (versionCode 62): a4696329b929f27422cd38fd6b65a3a384a72732b36b6fe967807d2c3f87a92f
  • armeabi-v7a (versionCode 61): 94a5f9fc56bafc27284ed29078a0801d125e41ce03558cb2687129e07577fadd

Signing: v2 scheme, CN=CallPages Merchant; certificate fingerprint matches the verified assetlinks.json.

Known limitation

Real Google OAuth cannot be automated on cloud devices (no owner account), so the first real-account picker sign-in is verified by the owner on his own phone — the decisive test surface. The worker contract behind it (code mint → poll → atomic exchange) is unit- and staging-proven, and the app build itself is install- and flow-verified on two physical device models.

Download availability

The signed v1.4.1 APKs are downloadable from the production download page: https://callpages.me/android

Production downloads were byte-verified against these checksums on 2026-10-11 (callpages PR #221). The binaries are also hosted in this repository under downloads/ (PR #1, pinned commit 6a943c422451526b810680e6861f71019983e55a), which is what the callpages.me download route streams.

The APK files are still not attached as assets to this release: uploads to uploads.github.com return 401 Bad credentials through the automation's GitHub connector credential (the credential covers api.github.com only; the gh CLI token is likewise invalid). Attaching them here remains pending a GitHub credential that covers the uploads host — the production page above is the canonical download surface in the meantime.