Reproducible Build failed for v2.0.0

[IzzySoft]

and the diff indicates it might be a "dirty build":

• the APK states to have been built from aeb4b13
• the release tag points to 4 commits later
• whether I built from aeb4b13 or from the tagged commit (using git reset --soft so AGP embeds the correct commit hash again), results are the same
• the DEX diff very much suggests it was a dirty build (i.e. one with local, uncommitted changes and/or build artifacts remaining from prior builds)

If that indeed is the case, this release is lost for RB, and we must mark it "failed". Can you confirm?

diff.zip

[Sztorm]

Yes, the release was built from aeb4b13

I thought that since these 3 commits later only change the readme file and screenshots, the resulting build should be the same.

Now I cleaned the project and built from 4441f1a
This build somehow differs.. it may be the caused by the things you described here.

I'm going to replace the build in release section.

Thank you for your diligence.

[IzzySoft]

I thought that since these 3 commits later only change the readme file and screenshots, the resulting build should be the same.

It is, but it took an extra round to establish that. Both APKs are "identically wrong", so to say…

I'm going to replace the build in release section.

Please don't! Never replace what was already distributed, better make a fresh (maintenance) release. The APK of the current release was already distributed, so it won't be picked up again…

Edit: too late, I see. Quick check: yes, that would most likely have been RB…

[Sztorm]

Ok ok :D At this point I'll just make a patch with new content. I also restored old build and renamed new build to "com.sztorm.notecalendar-2.0.0-new.apk"

[IzzySoft]

You could make a "maintenance release" (e.g. 2.0.1), with just versionName and versionCode adjusted, if you want. If you have it there before 5 pm UTC, it would be picked up today – and the green shield would be up again.