Android Gradle Build (tg-ws-proxy-android)

Build Android APKs with Gradle wrapper tasks using --no-daemon.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ComradeSwarog/tg-ws-proxy-android --skill android-gradle-build-tg-ws-proxy-android
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Android Gradle Build (tg-ws-proxy-android)
Source: https://github.com/ComradeSwarog/tg-ws-proxy-android/tree/main
Command: npx skills add https://github.com/ComradeSwarog/tg-ws-proxy-android --skill android-gradle-build-tg-ws-proxy-android

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you build the tg-ws-proxy-android Android application into a usable APK while avoiding Windows PowerShell hangs caused by Gradle daemon interactive prompts.

Core Features & Use Cases

  • Debug APK build: Produces app-debug.apk from the project root using the Gradle wrapper.
  • Release APK build: Produces app-release.apk from the project root using the Gradle wrapper.
  • Non-blocking command fallbacks: Provides a guaranteed-non-blocking cmd /c alternative to prevent PowerShell from hanging.

Quick Start

Run the provided Gradle Debug build command from the project root using the Gradle wrapper with the --no-daemon flag to generate app/build/outputs/apk/debug/app-debug.apk.

Frequently Asked Questions about Android Gradle Build (tg-ws-proxy-android)

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my Android Gradle build hang in PowerShell?▼

An Android Gradle build often hangs in PowerShell because the Gradle daemon waits for interactive input. Running the Gradle wrapper with the --no-daemon flag prevents this blocking behavior.

How do I build a debug APK using the Gradle wrapper on Windows?▼

To build a debug APK, run the gradlew.bat assembleDebug command from your project root directory using the --no-daemon flag. This generates the app-debug.apk file under app/build/outputs/apk/debug.

What is the best way to generate a release APK without Gradle daemon issues?▼

The best way to generate a release APK safely is invoking gradlew.bat assembleRelease with the --no-daemon flag. This deterministic approach outputs the app-release.apk directly to app/build/outputs/apk/release.

Does the Gradle wrapper require a specific working directory for Android APK builds?▼

Yes, the Gradle wrapper requires the project root directory as the working directory for Android APK builds. Executing gradlew.bat from any other path prevents the build script from resolving project configurations correctly.

Can I use cmd to run Gradle if PowerShell is still blocking?▼

Yes, if PowerShell continues blocking, you can use a guaranteed non-blocking cmd /c alternative to execute the Gradle wrapper. This fallback forces the terminal to return control after the Android build finishes.

Where are the output APK files located after an Android Gradle build?▼

After an Android Gradle build, the output APK files are located under the app/build/outputs/apk directory. You will find the debug build in the debug subdirectory and the release build in the release subdirectory.