@zhz8888/dsh-android-emulator-helper

LIMITATIONS

Known limitations

- **A machine with no global Gradle cannot build a generated project.** `android_create_app` writes no `gradlew`, and `android_build_app` can only generate one by running the `gradle` it finds on `PATH`; without one it fails with an explicit message. Install Gradle once, or run `gradle wrapper` in the project root yourself. - **Linux is unsupported**, exactly as in the original; `android_preflight` reports it. - `android_start_emulator` always starts a new emulator and never reuses one. Pass `serial` to the other tools to reuse a target. - `android_create_avd` always answers `no` to `avdmanager`'s confirmation, so it can never silently trigger a multi-gigabyte image download; install the image with `sdkmanager` first. - UI automation depends on the device-side `uiautomator`. When it is unavailable `android_ui_status` reports that, and the build, run and screenshot paths are unaffected. - The configuration page's installed-image list comes from scanning the SDK directory, not from `sdkmanager --list_installed`, which fails in restricted environments and prefixes its output with deprecation notices. - The configuration page's two routes are served by the plugin and are mounted in a real profile, but their HTTP responses cannot be exercised outside the GUI: the desktop app authenticates every request, so a bare `curl` to `/api/android-emulator-helper/status` answers `403 forbidden` before the handler runs. The page's spacing, dark theme and narrow-width wrapping still deserve a human look in the GUI. - No credential handling: the plugin never reads or forwards key/token/secret environment variables.