AI Agent Hub
Back to plugins
⚙️

DSH-plugin-android-apk

Workflow Updated 2026.08.16

Run the following command in DeepSeek Harness:

dsh plugin install memories-coder/DSH-plugin-android-apk

Paste the following prompt into your AI chat to install this plugin:

In DeepSeek Harness, tell the AI: Please install this DSH plugin for me: https://github.com/memories-coder/DSH-plugin-android-apk

About this plugin

Building an Android APK inside an AI workflow used to mean manually installing a JDK, configuring the Android SDK, fetching a Gradle distribution, and handling license acceptance. One missing piece and the conversation stalls. DSH-plugin-android-apk collapses the entire toolchain provisioning and build into a single plugin: point at a project folder, and it handles everything from download to delivering the final APK. All artifacts stay inside the session working directory; the user profile is never touched.

Core capabilities: it detects Gradle-based Android projects (settings.gradle, settings.gradle.kts, or a usable Wrapper), downloads Temurin JDK, Android commandline-tools, and the matching build-tools and platform on demand, writes local.properties, and accepts licenses automatically. It then runs assemble (debug or release) and copies the resulting APK to your chosen output folder. When a project or SDK path contains non-ASCII characters that break AAPT2 on Windows, the plugin stages both into a clean ASCII temp directory, builds there, and copies the APK back; the staged SDK is cached so nothing is re-downloaded. Under restricted networks, JDK, Gradle, and SDK downloads all fall back to Tsinghua, Tencent, or Aliyun mirrors automatically. Everything is configurable via parameters like variant, gradleVersion, compileSdk, and downloadDir.

This plugin is ideal for developers who iterate on small Android utilities, internal apps, or modules within DSH, particularly those in mainland-China networks who would rather not pause the AI conversation to fix yet another missing-toolchain problem. Specify the project path and build variant; the rest is handled for you.

Use Cases

  • Build an APK from a project folder with a single prompt in DSH
  • Provision JDK, Android SDK, and Gradle automatically on a clean machine
  • Auto-stage to an ASCII temp path when non-ASCII project paths break AAPT2

Best For

  • Developers iterating on small Android utilities or internal apps within DSH
  • Developers on restricted networks who cannot easily reach Google or Gradle mirrors
  • Developers who want AI conversations to stay unbroken by toolchain setup issues