[ci-scan-net11] Android UI tests cannot start because Emulator_30 is missing
- Dominant language
- C#
- Stars
- 23.3k
- Forks
- 2k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 296
Description
## Summary
The Android API 30 UI-test leg cannot start because the expected `Emulator_30` AVD is absent, and emulator boot subsequently times out.
## Build Information
- **Pipeline**: maui-pr-uitests
- **Build**: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1558104
- **Build ID**: 1558104
- **Branch**: net11.0
- **First seen**: 2026-08-18
- **Occurrences**: 1 in last 10 builds
## Affected Legs
- Android API 30 / Controls SoftInput, Stepper, Switch, SwipeView
## Error Message
```
2026-08-18T20:55:29.9149803Z Error: There is no Android Virtual Device named 'Emulator_30'.
```
## Recommended Action
Check the Android API 30 system-image provisioning and AVD creation step for this UI-test job, then verify that `Emulator_30` exists before the test runner attempts to boot it.
Contributor guide
Research direction
Start with the maui-pr-uitests Android API 30 system-image provisioning and AVD creation step, then inspect how the test runner expects Emulator_30 to be named. Verify that the API 30 image is provisioned, Emulator_30 exists, and the UI-test leg can boot the emulator without timing out.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- ci-cd, mobile, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100