Cannot build v2.0

[IzzySoft]

When trying to build from the tagged commit, build fails with

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

For more on this, please refer to https://docs.gradle.org/8.13/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
2 actionable tasks: 2 executed
  :app:releaseRuntimeClasspath -> androidx.navigation:navigation-fragment:2.9.5 -> androidx.navigation:navigation-common:2.9.5 -> androidx.navigation:navigation-common-android:2.9.5 -> androidx.navigation:navigation-runtime:2.9.5
  :app:releaseRuntimeClasspath -> androidx.navigation:navigation-fragment:2.9.5 -> androidx.navigation:navigation-common:2.9.5 -> androidx.navigation:navigation-common-android:2.9.5 -> androidx.navigation:navigation-runtime:2.9.5 -> androidx.navigation:navigation-runtime-android:2.9.5
  :app:releaseRuntimeClasspath -> androidx.navigation:navigation-ui:2.9.5

I see the APK was not built from the tagged commit, but claims to come from a83f31e – which doesn't match the versioning (at that point, versionName is still 1.6.1) – so I guess the APK was not built from a clean tree (with no uncommitted local changes, and no artifacts remaining from prior builds) either.

Is there anything we can do at our end to have a successful build – ideally with an APK matching yours? Background are Reproducible Builds we offer at IzzyOnDroid.

[TrueMLGPro]

Hello! Thank you for bringing this up. I was in a rush when preparing the 2.0 release so I think I built the APK before pushing the commit so this might've caused this confusing versioning to happen.

I'm gonna try to build from a new clean project to help you get Reproducible Builds going!

[IzzySoft]

• 76a5e21 (the tagged commit) just updates the Readme.
• the previous 2 commits, 77abb9f & d1ce281 are identical concerning their changes (the latter is just an extra merge commit).
• a83f31e (the commit hash embedded into the APK) still has the previous version in build.gradle

We checked out the tagged commit, and just used git reset --soft to the embedded commit. Due to the embedded commit hash, the APK cannot have been built from the tagged commit – and as the APK identifies as v2.0, it cannot have been built from the embedded commit either. There is no other option in between, which means you must have built the APK from a "dirty tree" then (with local, uncommitted changes), and having added more changes before you committed. This makes RB impossible, as we do not have a "common point" to build from (that was lost once you added more changes without a prior commit).

To give you some guidance, please take a look at our RB Hints for Developers – here, especially at what that document calls the "first basic rule", to always build from a clean tree at the tagged commit 😉

So, thanks for checking – and we're looking forward to your next release then. If you want to, we can check your intended release APK before you tag the release; all we'd need for that is an APK, plus the commit hash you built it from (which should be the one embedded into the APK, so we basically get it along).