Build issues with v1.7.0: missing commits?

[IzzySoft]

I don't know what the APK at v1.7.0 was built from – but we cannot build it reproducibly here:

Did you forget to push something?

[greenbugx]

Hey @IzzySoft I did push everything but this time I "Squash and Merge" the PR. Maybe that is the problem? Also I deleted the branch "dev/v1.18" after I merged the PR? Im clueless...

[greenbugx]

ok nvm, my bad I didn't create the Tag in the main branch, now its solved, check again please.

Also, fulldescMD did not update I guess?(not opening a separate issue now if you are here, LOL)

[IzzySoft]

Problem is: you now replaced an existing tag/release – which was already distributed (e.g. the APK was pulled to the IzzyOnDroid repo yesterday). Luckily, you seem to have attached the same APK again – but was it built from the tagged commit? The APK our builders generated from the tag, does not match yours:

  -rw-r--r--  0.0 unx       46 b-       48 defN 1981-01-01 01:01:02 b8ff6554 META-INF/version-control-info.textproto
- -rw-r--r--  0.0 unx      848 b-      848 stor 1981-01-01 01:01:02 a738f16b assets/dexopt/baseline.prof
- -rw-r--r--  0.0 unx      161 b-      161 stor 1981-01-01 01:01:02 3e618dd5 assets/dexopt/baseline.profm
- -rw-r--r--  0.0 unx  3357848 b-  1559110 defN 1981-01-01 01:01:02 86e65290 classes.dex
+ -rw-r--r--  0.0 unx      934 b-      934 stor 1981-01-01 01:01:02 8b7f2bd6 assets/dexopt/baseline.prof
+ -rw-r--r--  0.0 unx      161 b-      161 stor 1981-01-01 01:01:02 3c643703 assets/dexopt/baseline.profm
+ -rw-r--r--  0.0 unx  3357516 b-  1558747 defN 1981-01-01 01:01:02 ace79824 classes.dex
  -rw-r--r--  0.0 unx  7865264 b-  3162995 defN 1981-01-01 01:01:02 8d1a3460 lib/arm64-v8a/libapp.so

Unfortunately, if the build doesn't happen in the project root (with Flutter, it happens in the android/ directory), AGP does not properly embed vcsInfo – so we cannot determine which commit the app was built from.

To not "cause a mess", may I suggest we mark v1.7.0 "RB failed" – and hope the next release will be fine again? Chances for that are good, when you stick to the "first basic rule" in our RB Hints for Developers – and build the app from a clean tree at the commit the tag points to.

Also, fulldescMD did not update I guess?

No – you've updated that with a commit following the tag. Metadata are also taken from the tagged commit 😉

[greenbugx]

@IzzySoft Thanks for checking!

I'll make sure future releases are tagged directly from the main branch and built from a clean tree.

[IzzySoft]

Thanks! 🤗