Skip to content

[R5] Correct development iOS capabilities and validate simulator launch - #7162

Closed
antuz123 wants to merge 442 commits into
sprintfrom
codex/r5-ios-dependency-diagnostics-20261024
Closed

antuz123 wants to merge 442 commits into
sprintfrom
codex/r5-ios-dependency-diagnostics-20261024

Conversation

@antuz123

@antuz123 antuz123 commented Oct 24, 2026 •

Copy link
Copy Markdown
Collaborator

State: CLOSED_SUPERSEDED_NOT_ACCEPTED

Superseded by #7164, published source a23d9a9c92cb4cdddca03e07844a722805f74f24. This draft's complete source history is incorporated in that candidate.

This administrative closure grants no native, physical, security, combined R5 or release acceptance. All prior failures, NOT RUN items, handoffs, source-specific evidence and physical-scope decisions below remain unchanged. Continue work in #7164.


Keeper currently builds on the hosted iPhone simulator, but its launch is denied by the OS before the first passcode screen. The previous exact-head run remains a failure: https://github.com/KeeperCommunity/bitcoin-keeper/actions/runs/40110349118 (attempt 1, source b4bf96a). Its dependency setup, app build, installed-byte checks and Maestro driver readiness passed; later app scenarios did not run.

This change updates only the development target's obsolete armv7 device capability to the existing production arm64 requirement. It also adds a bounded, read-only, failure-only projection of owned simulator launch-service records, because an app-process-only query cannot explain a denial before a process exists. The capability correction is reviewed source configuration; it is not yet a proven explanation or fix for the OS denial.

Exact head: ed71b2e; tree 97e4f1b7feaae677b445e8dc649913d3e38c680e. Five changed paths against b4bf96a: development Info.plist, existing native driver/observer, and two focused regression files. Production configuration, dependencies/locks, signing, Android, UI assertions/waits, scenario counts and canonical authority are unchanged.

Verification: focused baseline controls fail on the previous source and pass on this candidate; full offline source/policy checks, clean-input fences, independent exact-source review and root review pass. No native pass transfers between heads. One additional iOS-only cloud validation of this exact candidate is authorized to test the capability correction and, if launch still fails, retain only the bounded OS denial observations. No identical-source retry is authorized.

Earlier outcomes remain preserved: dependency-only run40104929679 SUCCESS on64ae, original dependency run40104032087 FAILURE on183, full run40106112950 FAILURE ondc4239 before app launch, and full run40110349118 FAILURE onb4bf96 after driver readiness. See #7162 (comment) for the previous terminal receipt.

Codex local handoff

State: NEEDS_LOCAL
PR: #7162
Base: sprint
Head branch: codex/r5-ios-dependency-diagnostics-20261024
Head commit: ed71b2e
Goal and acceptance criteria: resolve the simulator launch denial, reach the first passcode screen, and report actual later scenario outcomes separately.
Changes made: development CPU capability parity and bounded failure-only launch-service observations, preserving the previously reviewed immutable dependency and driver setup.
Cloud checks: offline source/policy/focused regression checks and independent/root review PASS; current-head iOS native execution NOT RUN at source selection. Previous-head failures preserved.
Required local checks: IOS, ANDROID, HARDWARE
Local checks requested: actual hosted iOS/Android native acceptance plus separately scoped physical phone/signer checks; this one selected run is IOS only and requires no personal Mac.
Risks / known gaps: launch-denial cause and effectiveness of the capability correction remain unverified; combined R5 acceptance and protected-source evidence absent. No merge, production release signing, store upload, distribution or deployment.

redkeep-agents and others added 30 commits October 13, 2026 03:58
(cherry picked from commit eec419948e1ea132bd233741855d9037e9c8d1d4)
@antuz123 antuz123 changed the title [R5 diagnostic] Freeze Ruby dependencies and isolate iOS install [R5 diagnostic] Pin the root Ruby bundle and preserve fresh iOS installs Oct 24, 2026

Copy link
Copy Markdown
Collaborator Author

Selecting one corrected dependency-only check on exact64ae7b53ac8a363a20287afc135ea33eeb428510/tree4b5d821e27f47d73d2278d192aee9f4ee0f2121f after peer/root source review. The native opt-in was removed and verified absent before the fast-forward; old183/failure40104032087 remain preserved. Synchronization run40104881705 actually SKIPPED iOS, Android and preflight; current head/remaining dependency modifier and no competing native run verified. Add native-diagnostic once. This run must prove the actual ROOT Gemfile/lockfile and CP/Xcodeproj versions from ios/ before the strict pod install. No full app/driver/simulator/UI, no retries/source advance, no historical cause/acceptance claim. The reviewed first-launch correction is present but stays NOT RUN in dependency-only mode.

antuz123 commented Oct 24, 2026 •

Copy link
Copy Markdown
Collaborator Author

Corrected ROOT-bundle dependency-only run40104929679/attempt1, exact64ae7b53ac8a363a20287afc135ea33eeb428510, is terminal SUCCESS. Actual hosted Ruby validation from ios/ confirmed ROOT/Gemfile and ROOT/Gemfile.lock with CocoaPods1.16.2/Xcodeproj1.27.0 (exit0/0.7s). Frozen bundle install/check passed; strict pod install --deployment passed (exit0/127.4s). All four committed lock hashes match exactly before/after; final source/lock and Node overlay checks passed. Official run/attempt/head/artifact identities rechecked after decoding. Artifact12564552517 SHAef2f0207b6f19ba807f78b776cd741798fbbae68d5b225836ce2b8b9b514cda3; metadataSHAd1d186baaa0a5d21ae870d606df0d98faf1ba6326c027b5d8fc8fe69bb3bb30f.

This closes the frozen dependency-preparation check on this head. Driver/build/simulator/UI/persistence/workers/product, Android and preflight were actually SKIPPED; all app/native fields remain NOT RUN. This gives no first-screen, R5 or release acceptance. The original183 source/failure is preserved; the source-confirmed nested-Gemfile context defect is corrected and the bound route is now actually proven. The older ecb7 CocoaPods failure and launch causes are not retroactively established. Full iOS remains held until root reviews the final consolidated first-launch/capture source; no retry, source advance or release operation was performed.

@antuz123 antuz123 changed the title [R5 diagnostic] Pin the root Ruby bundle and preserve fresh iOS installs [R5 diagnostic] Stabilize frozen iOS preparation and fresh first launches Oct 24, 2026

Copy link
Copy Markdown
Collaborator Author

Selecting ONE full iOS-only diagnostic on frozen dc4239d after final root/peer combined review (root421Python/39Node PASS). Exact64ae dependency-only run40104929679 completed SUCCESS with actual root Gemfile/lockfile, CP1.16.2/Xcodeproj1.27, strict pod exit0 and all fences; that remains separately scoped. Native opt-in was removed and verified absent before the fast-forward and mode change. Old-head modifier40106023584 and dc synchronization40106032436 actually SKIPPED all app/preflight jobs. Current head/draft and ios-only modifier were verified; dependency-only modifier is absent. The sole parallel Android run40105347015 has iOS/preflight actually SKIPPED and a separate Android job, so there is no competing iOS selection.

Add native-diagnostic once. This full run must execute its own frozen preparation and actual first-screen/passcode smoke on dc, then report native persistence, workers and product phases separately. The default full acceptance obligations and Android/hardware requirements are not waived. Keep source frozen; no further native run/retry/cancellation/source advance or release operation without root.

antuz123 commented Oct 24, 2026 •

Copy link
Copy Markdown
Collaborator Author

Full iOS-only run40106112950/attempt1, exactdc4239d0bc48af3fa3a635e717abb2091908c2f1, is terminal FAILURE. Its own frozen dependencies, actual root Ruby context, pre-build iOS driver readiness, 1489.9s development build, ad-hoc signature/entitlements and pre-UI installed-byte proof PASS. Startup failed BEFORE any Keeper launch or UI command: Maestro's XCUITest driver did not answer its status endpoint, with IOSDriverTimeoutException/ConnectException; JUnit missing, zero command rows/hierarchy snapshots and no owned app-launch invocation. Persistence, workers, product and Android were SKIPPED. This is a test-driver readiness failure, not a proved Keeper startup fault.

Artifact12565164106/8238B SHAb04eeccb6066a44b5840ff6edb77698b4fc728bca663de8275d013ae810cf4f6; metadataSHA57c4e5abe0e4e3e37bfa03c168c696037650b41112b3fcd2f4e53401d91109a4. Source and failed run remain preserved. Pinned Maestro2.11's SDK defaults120000ms, but its own macos-15-intel/iPhone16/iOS18.5 CI configures240000ms. A bounded source proposal aligns that driver-only setting and outer setup allowance; app UI waits/performance requirements and Android remain unchanged. It is not yet a proved fix or native pass. No identical-source retry, source advance, new native run or release operation has occurred.

@antuz123 antuz123 changed the title [R5 diagnostic] Stabilize frozen iOS preparation and fresh first launches [R5 diagnostic] Apply the pinned Maestro iOS CI startup configuration Oct 24, 2026

Copy link
Copy Markdown
Collaborator Author

Selecting the ONE bounded follow-up for the iPhone R5 verification-driver fix on exact b4bf96a/treece56624cb1cdc7cb3e2c776ca49a3624a5fe7745. Root/independent peer reviewed the three-path change and the real-child baseline-red/fixed-green configuration contract. It applies the pinned vendor's own 240000ms iOS CI driver setting, adds only120s outer setup margin, and leaves app UI waits, product performance, Android and all authority controls unchanged. This is not a proved sole cause/remedy until the actual run.

The native opt-in was removed and verified absent before the normal fast-forward; prior dc failure is retained. Synchronization run40110235315 actually SKIPPED iOS/Android/preflight. Exact head/draft/ios-only modifier verified; queued/in-progress snapshots have no competing native run. Add native-diagnostic once. Goal: obtain actual first-screen/passcode evidence, then separately report later release checks. No further native run, identical-source retry, source change, cancellation or release operation is authorized by this selection.

antuz123 commented Oct 24, 2026 •

Copy link
Copy Markdown
Collaborator Author

Codex local validation

State: LOCAL_FAILED
Tested commit: b4bf96a
Run: https://github.com/KeeperCommunity/bitcoin-keeper/actions/runs/40110349118 (attempt 1; iOS job 120920570068)

iPhone R5 verification remains blocked at application launch. The actual Maestro driver became ready in both preflight and the startup attempt; no driver-startup timeout was observed. The pinned CI setting was 240000 ms with the separate 120-second outer setup margin. Preflight completed in 137.0 seconds; the startup command returned failure after 292.1 seconds.

The frozen root Ruby context, strict CocoaPods install, development simulator build, ad-hoc signing and pre-UI installed-artifact checks passed. Maestro then invoked the owned simulator launch and recorded LAUNCH_APP failure with FBSOpenApplicationServiceErrorDomain / 1. The first passcode screen was not reached. The post-failure installed bundle still matched the original built bytes, verified its ad-hoc signature, matched the complete entitlements and contained no internal links. The cause of the OS launch denial is unresolved; this result does not establish an app-data fault or copy corruption.

iOS build/simulator: BUILD PASS / STARTUP FAIL
Android build/emulator: SKIPPED in this iOS-only run
R5 persistence, workers and product scenarios: NOT RUN because startup failed
Real devices/signers: NOT RUN
Release readiness: NOT READY; candidate diagnostics are not protected-base acceptance.

Safe metadata artifact: 12567900404, 8573 bytes, SHA-256 f7801fc5db0ff58f1549c8fad2f15ba88d94deb0bdb9a2091cf0fb1a40892cdd.
Metadata member SHA-256: 9462a6e4bf21b13a3ce65c91ced8b73a78eb1b1f84aef74069ad6277168a7524.
Official terminal run, artifact digest and current PR head were independently rechecked after decoding. Only finite safe observations were retained; the downloaded ZIP was purged.

Open issues / next action: resolve the simulator OS launch denial with a source-supported fix and bounded diagnostic evidence before another native selection. This run exhausted the current authorization for one additional iOS validation; no identical-source retry, further run, merge or release action has been selected. The work uses hosted macOS and requires no personal Mac.

Development Debug and Release both require iOS 15.1 and use the legacy armv7 requirement. Match the existing production arm64 capability and Apple guidance for 64-bit apps. Add a source-bound regression for the active configurations. This is a source-only proposal; simulator launch causality is not established.
The actual iOS attempt passed driver readiness and verified the original installed app but received a generic FrontBoard launch denial before any first screen. The existing app-process-only log query cannot see an OS denial before app startup. Read system launch-service logs on the same owned simulator and original startup window, projecting only fixed services, allowlisted domain/code pairs and finite markers. Keep raw output in a closed private temporary file; observer failure cannot replace the startup failure or grant acceptance. No rerun is selected by this commit.
@antuz123 antuz123 changed the title [R5 diagnostic] Apply the pinned Maestro iOS CI startup configuration [R5] Correct development iOS capabilities and validate simulator launch Oct 25, 2026

Copy link
Copy Markdown
Collaborator Author

One additional iOS-only cloud validation has been selected at exact head ed71b2e: https://github.com/KeeperCommunity/bitcoin-keeper/actions/runs/40158447604 (attempt 1). This tests the reviewed development capability correction; the previous launch-denial cause is still unproven.

Independent all-path peer review and root review cleared this exact five-path delta. Native opt-in was removed before the fast-forward; the synchronize run40158417288 actually skipped iOS, Android and driver-preflight. The source was then verified and exactly one native opt-in addition selected this run with the existing iOS-only modifier. No competing native run was active at selection.

This run needs no production signing or store credentials. It is diagnostic app execution on a disposable hosted simulator, not protected-canonical or release acceptance. Further identical-source rerun authorization remains zero. No merge, production signing, upload, distribution or deployment was performed.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants