You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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: SrS2225a/custom_uploader@1c80a9f. What can I do to get my CI workflow to work with the new changes?
This discussion was converted from issue #205 on March 21, 2023 15:02.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
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 thebuild.gradle
file to use my new path as you can see on this commit: SrS2225a/custom_uploader@1c80a9f. What can I do to get my CI workflow to work with the new changes?Thanks!
Beta Was this translation helpful? Give feedback.
All reactions