-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
zipalign not found cause signing failure #84
Comments
I have this issue as well and no change was made between runs using this task. |
Add env variable for use special build tools version:
You can get build tools versions by
|
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. |
I have the same issue |
This fixed it for me. I used 34.0.0. Thanks! |
Same issue here. It stopped working out of a sudden |
It seems as though the default build tools version |
Here's a small step that looks for the last available version of build tools and sets it as env variable
You can than use it in the r0adskill step as @marat2509 suggested
|
See r0adkll/sign-android-release#84 Signed-off-by: mueller-ma <[email protected]>
Some additional context on this since I also encountered errors - Github has indeed removed tools versions versions prior to 31 |
See r0adkll/sign-android-release#84 Signed-off-by: mueller-ma <[email protected]>
Since January 8 the `ubuntu-latest` image excludes Android SDKs prior to version 31 By default the `r0adkll/sign-android-release` package uses Android SDK 29. So the build would fail In order to fix that, we can set the `BUILD_TOOLS_VERSION` env variable to define which version `r0adkll/sign-android-release` should use Related doc: https://github.com/actions/runner-images/blob/main/images/ubuntu/Ubuntu2204-Readme.md Related issue: r0adkll/sign-android-release#84
Since January 8 the `ubuntu-latest` image excludes Android SDKs prior to version 31 By default the `r0adkll/sign-android-release` package uses Android SDK 29. So the build would fail In order to fix that, we can set the `BUILD_TOOLS_VERSION` env variable to define which version `r0adkll/sign-android-release` should use Related doc: https://github.com/actions/runner-images/blob/main/images/ubuntu/Ubuntu2204-Readme.md Related issue: r0adkll/sign-android-release#84
Since January 8 the `ubuntu-latest` image excludes Android SDKs prior to version 31 By default the `r0adkll/sign-android-release` package uses Android SDK 29. So the build would fail In order to fix that, we can set the `BUILD_TOOLS_VERSION` env variable to define which version `r0adkll/sign-android-release` should use Related doc: https://github.com/actions/runner-images/blob/main/images/ubuntu/Ubuntu2204-Readme.md Related issue: r0adkll/sign-android-release#84
* fix for release flow according issue discussion r0adkll/sign-android-release#84 * removed extra line * hardcoded build tools to 34 * created extra step to find out latest built tools for signing apk
* Specify last build tools version; r0adkll/sign-android-release#84
@r0adkll, please PLEASE consider adding mention of build tools to this Action's documentation. Pretty annoying that the Action's users are probably going to have to organically find their way to this single issue thread to find a fix for a basic setup. |
it works thank u |
This should be added to the repo's readme too... |
Hi @r0adkll
Signing was working find until yesterday. from today is giving below error.
This is a blocking issue.
The text was updated successfully, but these errors were encountered: