release builds

[IzzySoft]

May I kindly ask to take care release builds are "clean builds"? The APK at the current release was not only built from a different commit, but in addition with uncommitted changes (versionCode was increased for the build, but not committed). This caused Reproducible Builds to fail, despite the fact our framework was able to automatically adjust for the commit in this case. We had to manually adjust the build recipe to match the versionCode.

Thanks in advance! And if you're curious, please take a look at our RB Hints for Developers. Never hurts to know some basics 😉 (and those in the linked document are the "easy ones").

[googol-apps]

Thanks for letting me know about the issue. As you know, I’m learning as I create things, which sometimes leads to unexpected errors. Sorry for any inconvenience caused.

[IzzySoft]

No worries – we're all constantly learning (hopefully). And that often goes with making mistakes (yupp, same for me, I just had a big "ouch" yesterday, needing to apologize to several developers 🙈). For building locally, I recommend establishing an alias (or shell/batch script in the PATH) – something like: alias releasebuild="gradlew clean assembleRelease". That then takes care at least that there are no old artifacts remaining from prior builds – but it doesn't care about uncommitted changes. But I see you already found an approach taking care for both: using GitHub Actions for this 🤗 Great! Double-win btw: that way we not only can see which build steps you are using (to reflect changes with our builds) – but it also runs in a "known environment" we can adjust to when needed (build paths, OS, etc).

Looking forward to the next release then – and with optimism, at that! 🥳