Skip to content

Observe pinned Maestro replacement bundles after iOS startup failure - #7159

Closed
antuz123 wants to merge 434 commits into
sprintfrom
codex/r5-ios-maestro-path-observation-20261024
Closed

antuz123 wants to merge 434 commits into
sprintfrom
codex/r5-ios-maestro-path-observation-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.


The prior iOS-only diagnostic built successfully but failed at LAUNCH_APP. Its post-failure observer then rejected the installed app's pinned Maestro replacement basename before measuring bytes, signature or entitlements. This draft permits that exact producer name only in the failure observer, retaining the existing owned simulator/container/path checks and the original built inventory path.

Exact head: ecb7f6e82e98a3d4de635bc07e1f3038eea08247.
Tree: a815a9cf76bd496ef7b1f928a5fe10ce2fde1c9d.
Parent diagnostic source: 7c00dc22937f94111298350a767466354f239ba9 (#7157).
This is a three-path incremental correction over that parent; the PR retains its inherited R5 diagnostic candidate ancestry relative to sprint.

The admitted alternative basename is the fixed owned app ID, a hyphen, exactly 13 ASCII millisecond digits and .app, and requires pinned Maestro cli-2.11.0. Foreign names/devices, symlink escapes and late path/inventory changes remain unknown. Canonical acceptance helper/callers, production app/native inputs, dependencies, signing, workflows, smoke flow and deadlines are unchanged.

Validation: 396/396 Python controls passed on this exact head; independent review passed 16 targeted controls; root separately reviewed the full change and passed 16 targeted controls. Diff check and source fences passed. These are host-side controls using temporary trees and controlled tools, not simulator results. Native execution on this head is NOT RUN at draft creation.

Prior source-specific result: #7157 run 40084560886/attempt1, iOS job 120844708599, built successfully and failed at LAUNCH_APP, reporting FBSOpenApplicationServiceErrorDomain/1. Replacement observations were UNKNOWN/INSTALLED_CONTAINER_POLICY. The application launch-denial cause remains unknown; this correction provides no application fix, native pass or protected-base acceptance. Android diagnostics on other sources remain separate.

Codex local handoff

State: NEEDS_LOCAL
PR: this draft
Base: sprint
Head branch: codex/r5-ios-maestro-path-observation-20261024
Head commit: ecb7f6e
Goal and acceptance criteria: Obtain bounded post-failure observations of the actual owned Maestro replacement without changing launch behavior or granting acceptance; retain all complete product/native/physical requirements.
Changes made: Three-path failure-observer basename admission correction, adversarial controls and source-specific documentation over #7157.
Cloud checks: 396 Python PASS; independent 16 targeted PASS; root 16 targeted PASS; diff/source fences PASS. iOS, Android and physical checks on this exact source NOT RUN at draft creation.
Required local checks: IOS, ANDROID, HARDWARE
Local checks requested: Coordinator-selected iOS-only cloud diagnostic for the observation correction; Android/full product checks remain outstanding for this exact source where required. Genuine phone/signer checks require authorized devices/testers. The owner's personal Mac is not required.
Risks / known gaps: Launch cause unknown. Observation correction is unvalidated on a simulator. Pre-merge diagnostics are not protected-base/native acceptance; no pass transfers across heads. No merge, release signing, upload, distribution, deployment or publication authorization.

redkeep-agents and others added 30 commits October 13, 2026 03:50
redkeep-agents and others added 22 commits October 22, 2026 23:31
Source-review join only. Tree is exactly B642fc14d1f2c3bd3451fe257642b01c6d1c07c95; second parent044ebb6ea2d465f6a70e9116e3feac5a604cd696 is preserved. Selected external thirteen-file work is exposed separately in C1 Android markers and C2 Maestro snapshot descendants. This join is not a native or release candidate.

Copy link
Copy Markdown
Collaborator Author

Coordinator-selected iOS-only diagnostic window on exact head ecb7f6e82e98a3d4de635bc07e1f3038eea08247, tree a815a9cf76bd496ef7b1f928a5fe10ce2fde1c9d.

Root exact-source review is CLEAR; 396 Python controls and independent/root targeted controls passed. The three-path change is failure-observation-only. The application's launch-denial cause remains unknown.

Selection order is deliberate: keeper/ios-diagnostic-only was added first. Modifier-only diagnostic run 40097557176 completed SKIPPED, with both actual iOS and Android jobs SKIPPED. Fresh PR metadata confirms this exact head, draft state, and only that modifier. Fresh repo-wide queued/in-progress snapshots show no active iOS native diagnostic. Existing non-native contract/CI jobs remain separate.

The next single keeper/native-diagnostic addition selects one iOS-only diagnostic. No Android diagnostic is selected here; no source advance, duplicate run, cancellation or retry is authorized. The coordinator is separately continuing an Android metadata reader on another source; results are not combined across heads.

Required IOS, ANDROID and HARDWARE obligations remain in the handoff. This run cannot provide protected-base native acceptance or approval to merge, sign, upload, distribute, deploy or publish. The owner's personal Mac is not required.

antuz123 commented Oct 24, 2026 •

Copy link
Copy Markdown
Collaborator Author

iOS-only diagnostic — terminal result for exact head ecb7f6e82e98a3d4de635bc07e1f3038eea08247

Run 40097580411/attempt1, iOS job 120882953541: FAILURE during immutable CocoaPods preparation.

Exact checkout/source guard, toolchain setup, frozen JavaScript install, repository patches, compatibility overlay, the pre-native lock fence, verified pinned Maestro download and pinned CocoaPods installation passed. The fixed pod install --deployment command exited 1 after 112.3 seconds against a 900-second limit. Its only retained failure category is COCOAPODS_ERROR. The underlying pod failure is undetermined; no failing pod, network/HTTP/checksum/spec-conflict detail or raw command message is retained. This is not an observed timeout. Initial disk preflight passed; that does not establish later disk state.

The intended measurement was not reached: driver readiness, app build, simulator startup and the post-Maestro observer did not run. Typed installed-bundle bytes, signature, identity and entitlements are NOT RUN. No evidence about the application's launch-denial cause was added. Persistence, worker and product checks were skipped; Android was actually skipped.

Existing safe metadata was downloaded read-only through the GitHub connector and its official digest verified. Artifact 12560679765, 2460 bytes, SHA-256 7b3c9250497669f1278525aebc3ceff1cc632eb485f3b08b3e215cf9dd2e54dd; the archive contains only ios/metadata.json. Workflow SHA e609b49831dc49d43b51d2e8ae7b6e131d76ce60 at refs/pull/7159/merge is recorded separately from the app head.

Compared with the preceding 7c00dc... run, the committed manifest/locks, preparation harness and workflow inputs are unchanged. Recorded runner image/OS, Node/Java/Xcode/SDK, compatibility/configuration overlay hashes and pinned Maestro match. The preceding pod command exited 0 in 124.9 seconds. That comparison does not prove a transient cause or provide a pass for this source.

Source remains frozen and clean. No retry, new native run or source advance is selected. A specific dependency measurement gap must be resolved before another full mobile diagnostic. This result grants no protected-base acceptance or release/merge approval. IOS, ANDROID and HARDWARE obligations remain open where required; no personal Mac is needed.

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.

3 participants