search

r0adkll / sign-android-release

A GitHub action to sign an APK or AAB
MIT License
362 stars 137 forks source link

Unable to sign APK file #8

Closed prin53 closed 4 years ago

prin53 commented 4 years ago

I am using the action like:

uses: r0adkll/sign-android-release@v1
with:
  releaseDirectory: ./
  signingKeyBase64: ${{ secrets.ANDROID_SIGNING_STORE }}
  alias: ${{ secrets.ANDROID_SIGNING_STORE_ALIAS }}
  keyStorePassword: ${{ secrets.ANDROID_SIGNING_STORE_PASS }}
  keyPassword: ${{ secrets.ANDROID_SIGNING_KEY_PASS }}

And getting the error:

[error]There was an error when attempting to execute the process 'C:\Program Files (x86)\Android\android-sdk\build-tools\29.0.2\apksigner'. This may indicate the process failed to start. Error: spawn C:\Program Files (x86)\Android\android-sdk\build-tools\29.0.2\apksigner ENOENT

Notes:

r0adkll commented 4 years ago

Could you try setting this secret on your repository (ACTIONS_STEP_DEBUG to true)? See (https://github.com/actions/toolkit/blob/master/docs/action-debugging.md).

This should print some extra debugging statements when you try to run the action. Please try this and post those logs here so I can better troubleshoot your issue.

prin53 commented 4 years ago

Using 1.0.1 version fixes issue for me, e.g. r0adkll/sign-android-release@v1 -> r0adkll/sign-android-release@v1.0.1.

What is strange, the v1 step has a different error now:

[error]No release file (.apk or .aab) could be found. Abort.

[error]No release file (.apk or .aab) could be found.

I am sure I have the .apk file in the repository root.

Maybe v1 should be unlisted, as GitHub Marketplace displays it as a default?

prin53 commented 4 years ago

My fault: I lost Checkout action, so the repo was not cloned.