Open Marco-9456 opened 3 months ago
Error: Error: ENOENT: no such file or directory, open 'app/build/outputs/apk/release/key.jks'
That error is a bit strange. One possible reason is, gradle assembleRelease
runs successfully, but app/build/outputs/apk/release
folder is not created.
Could you please:
sign-android-release
steppath
option of upload-artifact
to app/build/outputs/apk/release
To observe the operation and output files of gradle assembleRelease
itself?
An example of modifying the workflow:
- run: gradle assembleRelease
# - name: Sign app APK
# id: sign_app
# uses: ilharp/sign-android-release@nightly
# with:
# releaseDir: app/build/outputs/apk/release
# signingKey: ${{ secrets.SIGNING_KEY }}
# keyAlias: ${{ secrets.ALIAS }}
# keyStorePassword: ${{ secrets.KEY_STORE_PASSWORD }}
# keyPassword: ${{ secrets.KEY_PASSWORD }}
- name: Upload Artifact
uses: actions/upload-artifact@v4
with:
name: signed-apks
###################################
path: app/build/outputs/apk/release
###################################
if-no-files-found: error
retention-days: 20
If the workflow runs successfully, please pay attention to the log of the upload-artifact
step, which will output the full path of the unsigned apks. Please paste their full path in reply.
If the workflow runs successfully, please pay attention to the log of the
upload-artifact
step, which will output the full path of the unsigned apks. Please paste their full path in reply.
This is what I'm getting now:
Error: No files were found with the provided path: app/build/outputs/apk/release. No artifacts will be uploaded.
Error: No files were found with the provided path: app/build/outputs/apk/release. No artifacts will be uploaded.
Seems that I guessed it right - gradle assembleRelease
runs successfully, but app/build/outputs/apk/release
is not created. Maybe the generated apk is somewhere else, or gradle assembleRelease
did not compile and generate the apk at all.
Since your project still won't build properly without sign-android-release
enabled, there's not much I can do to help you. As my personal advice, I recommend:
app/build.gradle
to see if your build script specifies a different folder as the output directory for the apkgradle assembleRelease
to see if the apk has been generated, and where it was generatedThanks a lot, I'll see what I can do.
Hello, I'm recently getting the following error:
on: workflow_dispatch:
jobs:
build: runs-on: ubuntu-latest