Skip to content

ci: diagnose cloud iOS launch and Android onboarding failures - #7154

Closed
antuz123 wants to merge 429 commits into
sprintfrom
codex/r5-native-failure-continuation-20261024
Closed

antuz123 wants to merge 429 commits into
sprintfrom
codex/r5-native-failure-continuation-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 frozen d270 candidate builds on both platforms but fails iOS startup and Android's first full-product onboarding sample. The saved artifacts do not establish either cause. This continuation adds the missing bounded observations for one coordinated cloud diagnostic window.

Head: bea6056724dd75d1db99f4ce394ba4896edd10bf; tree: dbb87582dd05b075a3f0bfcac0fbdc68168fc534.
Review the seven-path delta against frozen d270. Full reviewed iOS 9910f9f7e4f9bca9a321ae96ce85a706dcc62bc9 and Android 127b94bda41a231ad8be0f23ace8cbaa69d0f886 ancestry is preserved.

Resulting behavior

  • iOS startup failure retains fixed Maestro command kinds/statuses, including a command left RUNNING after a connection exception, with evaluated-app binding. Fixed launch-stage markers and a read-only owned simulator service query supply bounded observations.
  • Android retains its original runtime-error queries and adds one separate fixed-prefix marker query. The former raw 1,200-line tail could omit earlier app markers before priority filtering. The new query has a 65-entry cap, 15-second timeout, existing bounded private reads and deletion, and preserves unknown/partial results.
  • Production app/native inputs, flows, signing, workflow files, acceptance deadlines and installed-byte checks are unchanged against d270. Original fix(ci): ad-hoc sign hosted simulator app for Keychain acceptance #7149 failures remain preserved. Cause, trusted acceptance, physical checks and release readiness remain open.

Validation

Combined source: 380 Python tests PASS; 1,430 Node controls PASS, plus 18 TypeScript-dependent controls PASS after providing the already pinned TypeScript5.0.4 tool dependency through command-scoped NODE_PATH. The initial three test-file load failures due to missing TypeScript remain recorded; no application dependency or lockfile changed. Both native workflow actionlint checks PASS (shellcheck/pyflakes unavailable). Diff/source scope checks PASS.

Both packages independently reviewed CLEAR. iOS peer: 122 Python checks plus eight extra canaries. Android peer: 30 targeted checks plus four extra canaries; fixed logcat source semantics independently checked. Hosted native execution on this new source has not run at PR creation.

Existing metadata-only readouts #7152/run40070128621 and #7153/run40078259072 passed for frozen d270 observations only. Android's captured failure is Start New visibility after Skip progress; the owned app was running and Skip remained represented in the post-failed-assert snapshot. Actual tap delivery and app cause remain unknown.

Cloud native execution

Frozen source run 40078818062/attempt1 is COMPLETED / FAILURE. Both platform jobs finished; this candidate is not natively accepted.

  • iOS job 120827882300: dependencies, driver readiness and development build PASS. Startup failed at recorded LAUNCH_APP sequence2 with fixed FBS_OPEN_APPLICATION_TEXT / SIMCTL_OPERATION_TEXT markers, before the Create PIN assertion. Clear-state/reinstall/permission return markers and exact owned simulator launch invocation were observed. The later read-only service query observed no owned entry; it does not establish launch history or the underlying denial cause. No owned app startup/error record was observed. Later persistence, workers and product phases were skipped.
  • Android job 120835800614: dependencies, build, startup, native persistence and controlled-adapter worker probes PASS. The first product sample failed at ASSERT_VISIBLE start_new_tile, command sequence35, after nine host acknowledgements through skip_tapped; the five-sample campaign did not complete. Metadata-only #7156/run40084255557 PASS, both source guards PASS, binds the exact retained artifact. The new marker query returned one owned ONBOARDING_EFFECT; missing Skip/reset/New Keeper stages remain UNKNOWN under positive-only coverage and unverified guest-clock freshness. A post-failed-assert snapshot still represented one enabled/clickable Skip node; actual tap coordinates, current visibility and tap delivery were not recorded. The app process/resumed activity and bound product Metro were observed; no product backend call was recorded. These facts locate the failed assertion, not its underlying app cause.
  • Retained iOS artifact 12555107520: 7,682bytes, ZIP SHA256 2c7630247cb958a828766acb9f5f16dba53856a94373c01cbb19e12f4e741691.
  • Retained Android artifact 12556810367: 9,632bytes, ZIP SHA256 c653b9d73044a8cc67cc098ff561d5a42f0a11d49013ae88dfa9edf5bf69df1b.

Official run attempt1 is bound to the frozen source and keeper-native-platform.yml workflow SHA fbb97bfe160e4b17d52bdf67aacc3f16aeb22f99, refs/pull/7154/merge. Original #7149 failures remain preserved. No Keychain correction acceptance, installed trusted acceptance, physical acceptance, merge or release authority is supplied. Source-only follow-up #7155 is separately reviewed preparation with native execution NOT RUN; no new native window has been started.

Codex local handoff

State: NEEDS_LOCAL
Base: sprint
Head branch: codex/r5-native-failure-continuation-20261024
Head commit: bea6056
Goal and acceptance criteria: Collect precise source-bound iOS launch and Android onboarding observations in one coordinator-selected cloud native window, retaining all actual failures.
Changes made: Seven .github/documentation paths described above; no production app change against frozen d270.
Cloud checks: 380 Python PASS; 1,430 Node plus18 TypeScript-dependent controls PASS; two actionlint checks PASS; independent reviews CLEAR.
Required local checks: IOS, ANDROID, HARDWARE
Local checks requested: Cloud-hosted macOS and Android diagnostics, no personal Mac. Existing physical obligations remain unrun and separate; no physical acceptance is supplied by this diagnostic.
Risks / known gaps: Both native causes remain unknown. No installed trusted-base acceptance, merge to shared branches, production/configuration change, release signing, upload or distribution authorization.

redkeep-agents and others added 30 commits October 13, 2026 03:38
redkeep-agents and others added 20 commits October 22, 2026 23:30
Source-review baseline only. Tree is exactly cd9d50a; second parent e343310 is preserved without producer rewriting. Its selected app and canonical collection changes are applied in separate reviewed descendants A and B. This baseline is not a native or release candidate.
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 cloud diagnostic window — 24 October 2026, 08:38 UTC.

Freeze head bea6056724dd75d1db99f4ce394ba4896edd10bf, tree dbb87582dd05b075a3f0bfcac0fbdc68168fc534. Reviewed full iOS9910 and Android127 ancestry is retained. Combined380Python controls PASS;1,430Node plus18TypeScript-dependent controls PASS, with the initial missing-TypeScript load failures preserved and corrected using the pinned5.0.4 tool dependency. Package peer reviews CLEAR; diff, unchanged production/native/flow/signing/workflow input checks and two actionlint checks PASS.

Fresh global queue read: zero queued runs; five running workflows are contracts/CodeQL/Ruby/CI/backend setup, with no active native app window. This PR's automatic legacy iOS/Android jobs and package-only Android diagnostic job are all terminal SKIPPED. The separate metadata readout7153 is terminal SUCCESS. The next label opts into exactly one diagnostic window, iOS followed by Android; no duplicate dispatch or cancellation is requested.

Keep this source frozen through terminal execution. Report actual stage outcomes and retained bounded facts; neither diagnostic observations nor host controls establish app causes, Keychain correction acceptance, installed trust, physical credit or release authority. Frozen7149/d270 failures, integration8b56, submittedR4/1d8 and the separate private security proposal remain unchanged. No shared-branch promotion, release signing, upload, distribution or deployment.

antuz123 commented Oct 24, 2026 •

Copy link
Copy Markdown
Collaborator Author

Frozen cloud native continuation — terminal result

Source remains bea6056724dd75d1db99f4ce394ba4896edd10bf, tree dbb87582dd05b075a3f0bfcac0fbdc68168fc534.

Selected run 40078818062/attempt1 is COMPLETED / FAILURE; both platform jobs finished. This candidate is not natively accepted.

  • iOS 120827882300: dependencies, driver readiness and build PASS; startup failed at recorded LAUNCH_APP sequence2 with fixed FBS/simctl-operation error markers. Clear-state/reinstall/permission return markers and the owned simulator launch invocation were observed. No owned service entry or app startup/error record was observed by later bounded queries. Underlying launch-denial cause remains UNKNOWN; persistence, workers and product phases were skipped.
  • Android 120835800614: build, startup, native persistence and controlled-adapter worker probes PASS; first product sample failed at ASSERT_VISIBLE start_new_tile, command35, after nine host acknowledgements through skip_tapped. Metadata-only #7156/run40084255557 and both source guards PASS. The new marker query observed one owned ONBOARDING_EFFECT; missing Skip/reset/New Keeper stages remain UNKNOWN under positive-only coverage and unverified guest-clock freshness. A post-failed-assert snapshot represented one enabled/clickable Skip node; actual tap delivery/coordinates/current visibility were not recorded. The process/resumed activity and bound product Metro were observed, with no product backend call. Underlying app cause remains UNKNOWN; five-sample campaign incomplete.
  • iOS artifact 12555107520: 7,682bytes, ZIP SHA256 2c7630247cb958a828766acb9f5f16dba53856a94373c01cbb19e12f4e741691.
  • Android artifact 12556810367: 9,632bytes, ZIP SHA256 c653b9d73044a8cc67cc098ff561d5a42f0a11d49013ae88dfa9edf5bf69df1b.

Original #7149 failures remain preserved. No Keychain correction acceptance, installed trusted acceptance, physical acceptance or release readiness. Separately reviewed draft #7155 supplies the next bounded iOS observation package; native execution there is NOT RUN. No duplicate/new native window, source advancement, personal Mac, release signing, store upload, deployment or merge.

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