Reproducible Build for v2.1.2 failed

[IzzySoft]

… and the diff is rather large. Almost looks like the APK was built from a commit other than the tagged one – though that's unlikely if it was built with the Github action. Using a Flutter pre-release might not be the best for a release either 😉

com.maelchiotti.localmaterialnotes.diff.gz

Any clue what might have gone wrong there?

[maelchiotti]

Sadly I couldn't build using the GitHub action, for some reason the pipeline requires too many things to be installed and the runner runs out of storage... But I didn't change the code since, so I don't think that's the issue.

I used a flutter pre-release because the latest version of the Mimir package uses a beta feature.

Anyway, that switch has mainly brought issues... Let's ignore this version, it's just small fixes. I'll make another version that reverts to the release channel and I'll make sure it's built with the action.

[IzzySoft]

Sadly I couldn't build using the GitHub action,

Ah, then my thought of it might have been built from a different commit might fit. Or from a "dirty tree" (uncommited changes, or artifacts remaining from prior builds – though different commit looks most likely). But if you built locally, we'd also need to change build paths etc to get it RB. So:

Let's ignore this version

The APK is already available in our repo. We'll then commit the logs of the failed RB, so it will get a shield saying RB failed. Next release will hopefully get the shield green again then.

Thanks for the explanations!

[maelchiotti]

Oh ok I see, well let's keep this issue opened until the next version and we'll check then that everything is fine.

[maelchiotti]

Hi @IzzySoft, I've just release a new version, hopefully everything will be fixed!