You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 4, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Jun 4, 2026. It is now read-only.
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...
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:
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 😉
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?