Automatic

[Love-tr]

name: Build APK

on:
push:
branches: [ main ]
workflow_dispatch:

jobs:
build:
runs-on: ubuntu-latest
env:
ANDROID_SDK_ROOT: /usr/local/lib/android/sdk

steps:
  - name: Checkout
    uses: actions/checkout@v4

  - name: Setup Java
    uses: actions/setup-java@v4
    with:
      distribution: temurin
      java-version: '11'

  - name: Install Android SDK command-line tools
    run: |
      sudo mkdir -p $ANDROID_SDK_ROOT
      sudo chown $USER $ANDROID_SDK_ROOT
      wget https://dl.google.com/android/repository/commandlinetools-linux-9477386_latest.zip -O cmdline-tools.zip
      unzip -q cmdline-tools.zip -d $ANDROID_SDK_ROOT
      mkdir -p $ANDROID_SDK_ROOT/cmdline-tools/latest
      mv $ANDROID_SDK_ROOT/cmdline-tools/cmdline-tools $ANDROID_SDK_ROOT/cmdline-tools/latest
      yes | $ANDROID_SDK_ROOT/cmdline-tools/latest/bin/sdkmanager --sdk_root=${ANDROID_SDK_ROOT} "platform-tools" "platforms;android-33" "build-tools;33.0.2"
  - name: Make gradlew executable
    run: chmod +x gradlew

  - name: Build debug APK
    run: ./gradlew assembleDebug --no-daemon

  - name: Upload debug APK artifact
    uses: actions/upload-artifact@v4
    with:
      name: app-debug-apk
      path: app/build/outputs/apk/debug/*.apk

[github-actions]

This GitHub issue outlines a GitHub Actions workflow for automating the process of building an Android APK. The workflow triggers on pushes to the main branch or via manual invocation (workflow_dispatch). It operates on ubuntu-latest and sets up the Android SDK environment. Key steps include checking out the code, setting up Java 11 using Temurin, installing necessary Android SDK command-line tools, configuring build tools and platform dependencies, making the Gradle wrapper executable, and running the Gradle task to build a debug APK. Finally, it uploads the generated APK as an artifact named app-debug-apk for access post-build. This automation streamlines the APK creation process, ensuring consistency and efficiency.