zipalign not found cause signing failure

[PINAKIN-KANSARA-EY]

Hi @r0adkll
Signing was working find until yesterday. from today is giving below error.
This is a blocking issue.

Error: Couldnt find the Android build tools @ /usr/local/lib/android/sdk/build-tools/30.0.2
Error: Unable to locate executable file: /usr/local/lib/android/sdk/build-tools/30.0.2/zipalign. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.

[donatellijl12]

I have this issue as well and no change was made between runs using this task.

[marat2509]

Add env variable for use special build tools version:

      - name: Sign Release
        uses: r0adkll/sign-android-release@v1
        id: sign_app
        with:
          releaseDirectory: app/build/outputs/apk/release
          signingKeyBase64: ${{ secrets.SIGNING_KEY }}
          alias: ${{ secrets.ALIAS }}
          keyStorePassword: ${{ secrets.KEY_STORE_PASSWORD }}
          keyPassword: ${{ secrets.KEY_PASSWORD }}
        env:
          BUILD_TOOLS_VERSION: "34.0.0"

You can get build tools versions by

ls /usr/local/lib/android/sdk/build-tools/

[PINAKIN-KANSARA-EY]

Add env variable for use special build tools version:

      - name: Sign Release
        uses: r0adkll/sign-android-release@v1
        id: sign_app
        with:
          releaseDirectory: app/build/outputs/apk/release
          signingKeyBase64: ${{ secrets.SIGNING_KEY }}
          alias: ${{ secrets.ALIAS }}
          keyStorePassword: ${{ secrets.KEY_STORE_PASSWORD }}
          keyPassword: ${{ secrets.KEY_PASSWORD }}
        env:
          BUILD_TOOLS_VERSION: "34.0.0"

You can get build tools versions by

ls /usr/local/lib/android/sdk/build-tools/

I have done that as well, it is failing for every build tool version we set.

[iteneum]

Add env variable for use special build tools version:

      - name: Sign Release
        uses: r0adkll/sign-android-release@v1
        id: sign_app
        with:
          releaseDirectory: app/build/outputs/apk/release
          signingKeyBase64: ${{ secrets.SIGNING_KEY }}
          alias: ${{ secrets.ALIAS }}
          keyStorePassword: ${{ secrets.KEY_STORE_PASSWORD }}
          keyPassword: ${{ secrets.KEY_PASSWORD }}
        env:
          BUILD_TOOLS_VERSION: "34.0.0"

You can get build tools versions by

ls /usr/local/lib/android/sdk/build-tools/

I have done that as well, it is failing for every build tool version we set.

Same here, it fails with all build tools in non hosted runners.

[ghraibeh]

I have the same issue

[donatellijl12]

Add env variable for use special build tools version:

      - name: Sign Release

        uses: r0adkll/sign-android-release@v1

        id: sign_app

        with:

          releaseDirectory: app/build/outputs/apk/release

          signingKeyBase64: ${{ secrets.SIGNING_KEY }}

          alias: ${{ secrets.ALIAS }}

          keyStorePassword: ${{ secrets.KEY_STORE_PASSWORD }}

          keyPassword: ${{ secrets.KEY_PASSWORD }}

        env:

          BUILD_TOOLS_VERSION: "34.0.0"

You can get build tools versions by

ls /usr/local/lib/android/sdk/build-tools/

This fixed it for me. I used 34.0.0. Thanks!

[muhammadarsal]

Same issue here. It stopped working out of a sudden

[Mihier-Roy]

It seems as though the default build tools version 29.0.3 doesn't exist on the ubuntu runners anymore. Specifying the version through an environment variable seems to work

[hamz4k]

Here's a small step that looks for the last available version of build tools and sets it as env variable

    - name: Setup build tool version variable
      shell: bash
      run: |
        BUILD_TOOL_VERSION=$(ls /usr/local/lib/android/sdk/build-tools/ | tail -n 1)
        echo "BUILD_TOOL_VERSION=$BUILD_TOOL_VERSION" >> $GITHUB_ENV
        echo Last build tool version is: $BUILD_TOOL_VERSION

You can than use it in the r0adskill step as @marat2509 suggested

      env:
        BUILD_TOOLS_VERSION: ${{ env.BUILD_TOOL_VERSION }}

[yairm210]

Some additional context on this since I also encountered errors - Github has indeed removed tools versions versions prior to 31