-
Notifications
You must be signed in to change notification settings - Fork 10
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
Failure to build app (APK/AAB) from source #1206
Comments
Thank you for the report @basantagoswami. Manual build is going to be fragile (and definitely not reproducible) due to lack of Flutter version pining. That's why we always use docker. I'm really surprised running
|
I am using Podman instead of Docker CE. I think the package name is
I will try using Docker Community Edition once and see if that works. Could be an issue with Podman itself. |
That seems to be the case. I just tried building with whatever podman comes with Ubuntu and get the exact same errors you did:
|
What mobile OS are you using?
Android
Please provide details on the device you experienced the bug on
No response
Description
I am trying to build the app from source as part of walletscrutiny.com's reproducibility tests. I checked out the latest release tag (v1.6.2) and tried out all the different approached outlined in the README, but failed to compile the code.
BUILDING MANUALLY
Flutter version:
Rust version:
As you can see this approach fails because of some version mismatch.
BUILDING USING DOCKER AND JUST
It fails because of some permission related issues with the steps in the Dockerfile
MY OWN APPROACH
just docker-build-android
. It failed at the last step (executingbuild_ffi_android.sh
), with this error:Please provide the steps that you've used to reproduce the issue
No response
If applicable, add screenshots or screen recordings to help explain the issue.
No response
If applicable, add logs to help us diagnose the issue.
No response
Anything else?
No response
Impact of the issue
None
If you found any similar or related issues, provide links to them here.
The text was updated successfully, but these errors were encountered: