subosito / flutter-action

Flutter environment for use in GitHub Actions. It works on Linux, Windows, and macOS.
MIT License
2.16k stars 193 forks source link

flutter build fails to produce an apk file when using another build path #205

Closed SrS2225a closed 1 year ago

SrS2225a commented 1 year ago

Hello,

So I am using flutter-action as my CI to detect error for my flutter app. However, I recently had the default build directory changed from ../build to /tmp/build as the team over at fdroid requested I enable reproducible builds as they expect my build to be built from there, and on thier side for reproducible builds to work (see: https://gitlab.com/fdroid/rfp/-/issues/2304 and https://gitlab.com/fdroid/fdroiddata/-/merge_requests/12469). But I noticed once I did so, the CI workflow for flutter build would keep erroring out with the message "Gradle build failed to produce an .apk file. It's likely that this file was generated under /home/runner/work/custom_uploader/custom_uploader/build, but the tool couldn't find it.". I think this is an issue with flutter-actions as on my local machine side, it would still find the apk file no problem. The only thing I changed was the build.gradle file to use my new path as you can see on this commit: https://github.com/SrS2225a/custom_uploader/commit/1c80a9ff1a702f01826b9a776d91a388b53ba598. What can I do to get my CI workflow to work with the new changes?

Thanks!