-
-
Notifications
You must be signed in to change notification settings - Fork 129
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
"Reproducible build" possible with Compose Destinations? #645
Comments
Hi @janexner 👋 What exactly do you mean? 🤔 |
Sorry, that was a little cryptic indeed. When you publish an app on F-Droid, they ask whether it's a "reproducible build", meaning would it be possible to create the exact same APK from the sources no matter where (e.g. my Android Studio versus the build pipeline that F-Droid uses on gitlab). A link they published: https://f-droid.org/docs/Reproducible_Builds Then there is a toold call diffoscope (https://diffoscope.org/) that you can (and F-Droid's pipeline does) use to compare APKs, and when I use diffoscope on my app, I get messages to do with Compose Destinations, such as these: I am now wondering whether Compose Destinations use any features that may lead to randomly assigned identifiers or anything like that, that would break reproducible builds. Disclaimer: I am totally new to F-Droid and reproducible builds. I know that if yours is, people can install from any source, and upgrade from any other, which I think is cool. It's obv possible that what I see has nothing to do with how Compose Destinations works, but that it is something in the/my toolchain. Hence my question. |
Also want to add that your library has saved me, literally. W/o Compose Destinations, I would never have been able to build what I built. Big thanks for that! |
I think I managed to create a reproducible build, so I shall close this. |
The answer is "Yes!" |
Is it possible to make a "reproducible build" with Compose Destinations?
The text was updated successfully, but these errors were encountered: