Izzy

It looks like, from what I can tell – and I trust you if you say so 😉 And yes, should something pop up, I surely will 🤣

Well… you requested @sunilpaulmathew, I promised – and there I am again. That release was not RB, only thanks to your `release.json`. Let me quote the part giving the clue:...

> Sincere apologies. Accepted 🤗 > This time, I think I made the commit, but haven't pushed them to repo before building APK. Is that the reason? Seems like –...

Ah, the next problem with the integrated updater I see 🙈 So it probably took the hash from the previous release then, as this one was not yet up –...

I'm just confused on how it can know the sha1 of an APK that has not yet been built 🤷‍♂️

> Release builds are built locally on my pc and I use JDK 21 on Android Studio. 👍 Will change the recipe to use 21 then. > Can you kindly...

> It's zipped, renaming didn't help Was too big, yeah. Note: Please avoid "blank characters" in file names (`Iconify v7.1.0` => `Iconify_v7.1.0`), those are far too often problematic in scripting....

That's Jetbrains, as expected. And looking at [ZIP ordering differences](https://gist.github.com/obfusk/f0460dcdb21396ba3d2cc9db56bb40ae#zip-ordering-differences): > [Bug: Android Studio builds have non-deterministic ZIP ordering](https://f-droid.org/docs/Reproducible_Builds/#bug-android-studio-builds-have-non-deterministic-zip-ordering) > Solution (upstream): either build using the CLI (not Android Studio)...

> I am actually trying to avoid manually singing each apk. And I want to handle release builds manually So manually without manually, OK, got it 🤪 You already have...

v7.2.0 has the identical problem still.