Skip to content

Add shared Tauri Android and iOS client build paths - #21

Merged
LIghtJUNction merged 12 commits into
mainfrom
feat/mobile-client-packaging
Nov 20, 2026
Merged

LIghtJUNction merged 12 commits into
mainfrom
feat/mobile-client-packaging

Conversation

@LIghtJUNction

@LIghtJUNction LIghtJUNction commented Oct 22, 2026 •

Copy link
Copy Markdown
Member

Purpose

Make the existing Tauri client available as Android and iOS engineering builds, using one mobile WebView and a responsive local connection screen. The current Android candidate now passes both the unchanged device regression and the actual native WebView → system Chrome → private server consent/return flow.

Changes and resulting behavior

  • Add the shared mobile library, platform initialization/build/verification commands, debug artifacts, and separate manual signing workflows.
  • Preserve the desktop release policy, selected-service navigation rules, and local-launcher-only native commands. Integrate the server flow already merged in Add one-time browser consent and safe native login return #24.
  • Correct a reproduced Android event-loop deadlock in the login-return callback. The existing WebView lookup, current path/origin checks and fixed payload-free notification now run in Tauri's blocking worker pool. The callback no longer synchronously waits for a URL query that must be serviced by the same platform event loop.
  • Keep the incoming single-URL whitelist, explicit browser consent, separate application session, and cold-start behavior that stays on the local connection screen.

Fixed candidate and merge tree

Item Exact identity
Validated head 5d9313df5dc9c295a2ab575107ed665b3a92dc19
Validated tree b6e3e5439705b6c94e04180734c8bfeb49c33e53
Current main used for merge validation dd3c20e40093892cf14f50fe09cd8c6c93350525
Predicted merge tree b6e3e5439705b6c94e04180734c8bfeb49c33e53
Engineering APK SHA256 935fc98fa8aa62ef84b6d12205f9216c6e8eaf2c9ffd3389bbe54a95a83c9b23

Main is an ancestor of this head. Native git merge-tree produced the exact validated tree with no difference from the tested checkout.

Completed Android acceptance — 2026-11-20

The engineering APK is best.lmm.hireferry.debug, x86_64, 42,747,530 bytes. Rust 1.100.0, JDK 21, SDK 37.0/build-tools 37.0.0 and the exact prepared NDK 29.0.13846066 were used. The cached build completed in 52.525 seconds. Restoring the original task-owned debug certificate required signing only; all 934 non-signature ZIP payloads were verified identical, and package/ABI/signature verification passed. No maintainer release key was used.

Gate Result
Original installed-APK regression Passed: installation, local launcher, remote workspace, native-command denial, feedback, non-overlapping controls, return to local screen, warm login return, and cold return staying local
Original UI deadlines Every application UI condition remains 45 seconds
Actual WebView request HttpOnly/SameSite=Strict proof stays inside the app; the public URL contains only the request identifier
Actual system Chrome consent The matching code is displayed; consent begins unchecked and approval disabled; the browser has no app proof and cannot redeem the request
Explicit approval and actual native return Passed through Chrome and the registered hireferry://login-return scheme
Application session isolation A distinct app session is created; the original browser session and its lifetime remain intact; replay is rejected
Native settings return Passed back to the actual local connection screen
Android diagnostics No HireFerry ANR/native crash in the fixed baseline; no ANR or crash in the successful joint run
Isolation and cleanup No external authentication requests; temporary server/database closed; owned emulator independently confirmed inactive/dead

The joint-only continuation completed in 113.911 seconds, including a 38.032-second API35 boot. It used Chrome 124.0.6367.219 and the real #24 server binary with verified identical server inputs. The passed baseline was reused by its exact receipt hash and was not rerun. All execution used the private emulator-5582 fixture, bounded resources, and the shared owner lock.

Preserved failures and the fixture correction

The prior application checkpoint 42d536d reproduced a 5,006 ms focus-event ANR, followed by SIGABRT. The captured Wry 0.57.0 panic identifies the queued URL reply sending to a receiver that had timed out. The final callback change directly addresses that event-loop wait, and the original device assertions now pass.

The first fixed-APK run passed the full baseline but stopped before joint login because the private Chrome launcher incorrectly supplied --disable-sync. Chrome read the flags and then produced a null-pointer SIGSEGV. The installed Playwright Android defaults explicitly omit that flag. The continuation removes this single launch flag, adds diagnostics, and leaves the actual application-flow assertions byte-identical. Chrome then exposed the requested debug socket and completed the real joint flow. The original crash, failed attempt and exact script hashes remain preserved; the native stack was not symbolized as an IdentityManager stack.

Earlier SDK-path, cache/signature-preflight, UI-dump readiness and boot-timeout attempts also remain separate evidence. None is recast as a successful application test.

Portable and iOS evidence

The recorded portable checkpoints passed 14 Python mobile tests, 4 JavaScript tests, and 7 Rust tests importing the actual navigation policy; formatting, syntax, locked metadata and documentation-link checks also passed. The final handler was subsequently compiled into and exercised through the Android APK above.

The historical iOS simulator job from run 39885106014 passed at its original merge source. This work does not claim a new current-source iOS device or simulator run.

Evidence locations and hashes

Durable development-machine evidence is under:

/home/lightjunction/Documents/GITHUB/pr-cleanup-org-20261120/evidence-hf21/

Receipt SHA256
android-fixed-smoke-1795205175/smoke/android-smoke.json 6991b9a95c394eb6fb0740ff3fa0c3dfd9598089bb17c092521aa189ad3dd599
android-fixed-joint.json faab8e9375bb15611914120786a360f0e201d4f2e7a6117e0f241dd89c2637a8
android-fixed-joint-1795206290/joint/native-app-login.json d5ded8a35f0b92fe9e3a90ca0e188da32d0c7bb914ed850d28f196e2cbc41f5b
android-chrome-preparation-diagnosis.json 7d81283e6e33c58fab36df71dfa255236ec03cd24cc5d69b6b2ead6da7a6a6e2

Build/signing provenance is in android-fixed-build-final.json; the application ANR diagnosis is in android-deep-link-anr-diagnosis.json. APKs, screenshots, userdata and logs remain outside Git.

Distribution boundary

This PR enables engineering builds. Formal server/CLI/desktop publication remains tag/manual controlled, and mobile signing remains an explicit workflow_dispatch operation using the mobile-signing environment. No release/tag, workflow dispatch, store submission, production-account login or physical-device acceptance was performed.

Reuse the desktop host with isolated mobile navigation, safe launcher return,
Android APK/AAB and iOS simulator/device build paths, signed release gates,
and truthful engineering artifact documentation.
Use the locked npm lifecycle when Xcode and Gradle re-enter Tauri, avoid
removed legacy Android SDK tools, and reject credential/query-bearing
server addresses before any local preference is saved.
Use the SDK's actual versioned package path and supported command-line tools,
collect the real iOS simulator architecture output, and add a parameter-free
app return signal without importing credentials or server URLs. Exercise the
Android launcher, remote navigation and native permission boundary.
… [skip ci]

Keep shared library entry points and current custom-protocol configuration; preserve responsive Web and signed-release boundaries. Record portable 9 Python,4 JavaScript and7 Rust policy checks while retaining the Android ANR gate.
LIghtJUNction added a commit that referenced this pull request Nov 20, 2026
…p ci]

Preserve current passkeys, session identities, source/referral inputs and migration behavior while integrating the native app-login grant flow.

Verified exact tree 2ba69fb: 112 Rust tests passed (one existing large-scale case ignored), actual server build, and all 8 real-server browser groups passed with Playwright 1.62.1. Original environment failures and the untouched-main migration assertion control are retained.

Current Android/mobile integration remains in draft PR #21; no native release, production deployment or real OAuth session is qualified by this merge.
LIghtJUNction and others added 2 commits November 20, 2026 23:40
…kip ci]

Bring merged server PR #24 into the mobile branch. Its 13 files do not overlap the 22-file mobile change; the complete resulting Git tree is checked against the exact source blobs from both parents. Desktop/mobile build inputs and the original Android return gate remain unchanged.

Server validation: 112 Rust tests and 8 real-browser groups passed on tree 2ba69fb. Current native Android acceptance is still in progress; this commit does not claim a platform pass or authorize distribution.
A real API 35 emulator launched the APK successfully but uiautomator returned before its XML existed. Poll fresh layouts within the original 45-second deadline, record probe output, and reject transport errors and stale XML. Preserve every application assertion and keep the APK unchanged. All 14 mobile packaging and probe regression tests pass.
The current API35 smoke reproduced a focus ANR on warm login return, followed by wry's GetUrl reply panicking after its receiver timed out. The return callback synchronously requested the current WebView URL from the same platform loop.

Dispatch the existing selected-origin and login-page checks to the blocking worker pool before sending the unchanged payload-free event. Keep the incoming URL whitelist and cold-start navigation rules intact.

Rust formatting and whitespace checks passed. Android rebuild, unchanged 45-second return checks, and the real native/server/browser integration remain pending; keep PR21 in draft. Reproduction and diagnosis: evidence-hf21/android-root-smoke.json and android-deep-link-anr-diagnosis.json.
@LIghtJUNction
LIghtJUNction marked this pull request as ready for review November 20, 2026 20:28
@LIghtJUNction
LIghtJUNction merged commit 0d900c2 into main Nov 20, 2026
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 20, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
🔒 Security Review ✅ Completed 2026-11-20T20:30:45.960019Z 5d9313d Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants