Repository navigation
Conversation
# Conflicts: # src/utils/service-utilities/config.ts
…afb05f # Conflicts: # .github/workflows/test.yml # src/hooks/useUSDTWallets.ts # src/screens/Home/components/Wallet/HomeWallet.tsx
…-264-combined-candidate
…-264-combined-candidate
|
Hosted contract evidence for exact head Labels remain empty. Hosted-native39870183663 and Android diagnostic39870186915 were SKIPPED; release/local gates remain blocking and their native platform jobs skipped. No native marker transport, app acceptance or physical pass on this head is claimed. Original1bc window39858617273/a1 completed naturally with both jobs finished; its own diagnostic label was removed only after fresh completed/attempt/source/zero-active-run checks. Its Android artifact12466091444 is being retrieved/audited before any new native window or correction. |
|
Selecting one hosted diagnostic window on frozen source Immediately before selection, repository-wide queued/waiting/pending/requested lists are empty and the only in-progress workflows are ordinary CI/CodeQL/public backend setup. There is no active native job. Original39824790868 remains completed failure/a2/3eb; latest39858617273 remains completed failure/a1/1bc. No retries/cancellations/duplicate native work. Newer-record review found no executed native result or startup/Keychain/PIN correction to adopt. The single existing keeper/native-diagnostic opt-in will serialize hosted macOS iOS then hosted Android. Preserve this source while the window runs. The new receipts are observations only: native marker transport, iOS original failure phase/status and Android original Skip/reset/effect/snapshot outcome are UNRUN until actual evidence arrives; cause remains unknown. Do not infer a fix or acceptance from setup/contracts. After diagnosis, make only an observed-cause correction and complete the exact-source full acceptance matrix. Physical checks remain UNRUN; no personal Mac, merge/deploy or release signing/upload. |
|
Independent hosted contract verification: run39872935132/a1, job120151496106 completed SUCCESS with 164 Node +294 Python PASS, no Node failures/cancellations/skips. Actual checkout was synthetic PR commit |
|
Ordinary CI evidence for frozen044 (run39872935066/a1): actual checkout was synthetic PR commit5a7b0c5da0a38197f6dd675ff424f3ba3f441d02, tree4856035ece888230674e061c53115de3d6f025ed equals the head tree. Tests job120151495933 passed50 Jest suites/788 tests,502 recovery Node controls,41 USDT/build-input Node controls,28 release Node+7Python,21 Android16KB static Python,10 reproducibility Python and version consistency. These are host/source controls, not native acceptance. The separate automatic-backup matrix job120151496108 failed: 2/295 passed,293 failed at snapshot setup. The same2/293 failure exists on1bc, e343 and current7068. Static loader/source tracing identifies incompatible inherited fixtures (invalid placeholder mnemonic/32-byte seed versus current protected authority’s validBIP39/matching64-byte-seed requirement) and retired endpoint expectations. Runtime retained only snapshot-request/non-transport, not the internal throw; do not claim this proves the sole cause of all293 cases. New startup/Splash diagnostics are outside its import graph. Dependency/Realm/Relay/Mongo readiness passed. Existing signed-v3 proof records/current recovery controls are scoped evidence; they do not green the old matrix. Lint job120151496051 reports SUCCESS through continue-on-error; actual lint exited1 with4453errors/882warnings, including two new prefer-destructuring findings in startup-failure-observer.ts. The frozen native window remains untouched. Existing authority checks will not be weakened to accommodate stale fixtures. New-head native startup/product/physical checks remain pending. |
Exact-source hosted iOS result — BLOCKEDSource
Typed installed inventory New observed boundary: exactly one owned in-window V1 receipt reports NATIVE_CREDENTIAL_READ / REJECTED / Error / -34018. Marker/own-process counts1; duplicate/malformed/foreign/outside/partial/cap counters0. This is the original native read rejection, not credential JSON/navigation failure or accepted empty-store false. Locked Keychain10.0.0 directly serializes SecItemCopyMatching’s failing status. Apple’s immutable SecBase.h:341 defines it as errSecMissingEntitlement: “A required entitlement isn’t present.” One parsed hierarchy shows credential-error andRetry true, Login/WelcomeBack/loading/LogBox flags false. The receipt lacks current-effect identity, so retain its bounded original-boundary attribution limit. Effective built entitlements were not queried; the particular absent/unusable entitlement remains unmeasured. The recorded build disables Xcode CodeSign, which does not exclude linker-generated ad-hoc signatures. Do not call all signature state absent. Metro retains11valid rows,4APP_WINDOW request/buildstart/builddone/outer200, noAPP_WINDOWERROR row, no invalid/truncation/cap; coverage BOUNDED_INPUT_ONLY. Own compact query SUCCESS/PARSED1975records/1032errorrecords,18CONNECTION/1014unclassified; other fixed categories0. Those aggregate error counts are not crash or causal proof. Exact metadata-only artifact12469536083:7232-byte ZIP SHA256 Next preparation is isolated: inspect actual effective Debug-simulator identity/entitlements, conditionally correct only the missing owned app identity using certificate-free simulator ad-hoc signing, and verify final identity before all byte fingerprints. No app Keychain error swallowing/options, dependency, flow or deadline correction is justified. Actual corrected acceptance remains UNRUN. Android job120167960772 started naturally and is building; preserve it. Source044/PR7131 remains frozen. No cancellation, rerun, duplicate native window, personal Mac, release signing/upload, merge or deployment. |
The completed exact-source window on #7116/1bc built both apps, then failed at iOS’s guarded credential-error UI and Android’s first full-product Start New assertion after Skip. Neither retained artifact identifies the cause. This draft adds bounded original-boundary observations before any behavioral or dependency correction.
Frozen head:
044ebb6ea2d465f6a70e9116e3feac5a604cd696Tree:
4856035ece888230674e061c53115de3d6f025edSole parent:
e34331083959c94b5f0a17603d8c1f578305c474The inherited iOS preparation records account-state, synchronous credential-call throw, asynchronous native rejection, credential-JSON and navigation phases. Only a native-read rejection may export a strict complete decimal int32 status. Fixed error enums and development-only native-hook markers preserve the original query, result/error, fail-closed UI and existing post-failure query. No credential, account/service identifier, message or stack is exported.
The new Android observer records entry to the existing onboarding effect, original Skip handler, synchronous reset return/throw and existing NewKeeper effect. The original reset arguments, one call, return value/error and effect cleanup remain intact. Fixed bounded development markers use the pinned RN native Error sink and the unchanged four-query collector. Missing markers remain UNKNOWN; guest-clock freshness is unverified. They do not prove tap delivery, route handling, visibility or cause.
A pure Maestro parser binds the failed assertion’s commands.json execution sequence to its SCREEN_HIERARCHY outcome and projects only fixed Skip identity count, bounded numeric geometry and native booleans. This is POST_FAILED_ASSERT_OUTCOME_NOT_TAP_TIME; coordinates at the tap and visible-to-user are not recorded. The optional receipt is adjacent at failed outcomes’ failed_assertion_snapshot; existing four-key failure_observation and pinned acceptance consumers remain unchanged.
No app correction, dependency, selector, flow, navigation action, retry, additional native query/process, build/signing configuration or deadline change. Independent review CLEAR, including actual TypeScript handler/effect controls, original-error/cleanup priority, source-format checks and pinned evaluator compatibility. Full local contracts PASS 164 Node + 294 Python, zero failures/skips (Node24.19.0/Python3.12.14, locked TypeScript5.0.4). Whitespace PASS. All 110 native command/subprocess ASTs and 74 timeout/error_details keyword values across the existing native Python harness match parent e343. Updated inherited Jest expectation itself remains NOT RUN locally; actual-boundary Node controls passed.
Historical evidence remains exact-source: completed 1bc matrix. Android1bc passed startup, native Realm/MMKV persistence, all five source-bound workers and pre-product installed APK checks; product sample1 failed at Start New with only startup_to_passcode_ms recorded. iOS1bc passed readiness/build/install/pre-UI bundle identity, then failed startup; later feature checks did not run. These results do not transfer to 044e. Earlier e343 hosted contract success checked out a synthetic PR commit with the same e343 tree; it is not a native pass or a direct-head checkout.
One hosted window is now selected: 39873063291/a1, frozen at044ebb6e, serializing iOS then Android. Selection record documents the fresh absence of other active/queued native work and unchanged original completed attempts. Do not push another source or cancel/rerun this window. iOS job120151926152 completed FAILURE at00:24:20UTC: dependencies, driver readiness and build PASS; startup FAIL; native persistence/workers/full-product checks SKIPPED/UNRUN. Artifact12469536083 (7232B; SHA256e244015128d4aa72e1e1c8be3072bc70d506ba11a804067448122d1318621caf) is being retrieved through the reviewed finite reader; phase/native code and cause are not yet evaluated. Android job120167960772 started naturally and is installing dependencies; do not cancel/duplicate it.
Codex local handoff
State: NEEDS_LOCAL
PR: #7131
Base: sprint
Head branch: codex/r5-startup-credential-failure-observation-20261022
Head commit: 044ebb6
Goal and acceptance criteria: Diagnose the original iOS startup/Android transition failures before a minimal correction; then complete exact-source persistence, five production workers, installed bytes, five full-product samples, separate Retry, key/PIN and companion checks.
Changes made: Original startup failure observation plus thirteen-file Android boundary/snapshot parser/test/documentation preparation; development observability only.
Cloud checks: Local164Node/294Python and hosted same-tree164Node/294Python PASS; actual Jest788/recoveryNode502 PASS. Legacy backup matrix2PASS/293FAIL and lint failures remain explicit in comment6354017588. iOS dependency/readiness/build PASS, startup FAIL, later native checks UNRUN; Android IN PROGRESS. Artifact evaluation pending. Historical passes remain bound to their own source.
Required local checks: IOS, ANDROID, HARDWARE
Local checks requested: Hosted macOS/Android only, serialized window coordinated without cancelling or duplicating existing work. Physical phones, biometrics, cameras, NFC/USB and real signers NOT RUN; no owner deferral.
Risks / known gaps: Startup/transition causes remain unknown. Full-product measurements, Retry, key/PIN and companion matrix remain incomplete. Premerge diagnostic infrastructure is untrusted for protected-base acceptance. No personal Mac, merge, deployment, release signing or upload.