-
-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build of v2.3.2 fails with lint errors #54
Comments
Oh shoot, I'll only be able to fix tomorrow night (GMT +1) |
For now I've kept the logs back, in the hope it can be fixed somehow on our end. You were able to build, so there might be a way, and unless it involves something cached on your end… Quick thought: If you really built from the very commit the tag points to, with no "dirty tree", maybe we could pass some As long as your APK is fine (and not broken), this is no big deal: the update itself was not held back, just the RB shield. That said: Good you have those lint checks in place, so such things are getting caught! 🤩 |
So here is what happened on my end : I removed some strings in english, I tried building the apk, got the lint error, added back the strings in english, tried building again and it worked ! As they are unused strings, I'll manually delete them from every language to be sure theres no errors Hope this makes everything abit clearer 🤗 |
And after you've added the strings back, you've committed those changes to the repo before building the app, or not? Because if not, what the verification builders get is the code with the strings missing, lint yelling and the build failing. Hence the "first basic rule" in our hints on reproducible builds say to always build from a clean tree at the commit the tag points to" 😉 |
Ah yes, classic me forgetting everything 🤦 |
Good to have a "human reminder", huh? 🤣 Next release should fix that then (don't change the already distributed one, please). |
Thanks, went through fine with yesterday's update batch 🥳 |
Unfortunately, the (reproducible) build of v2.3.2 failed, so this release will not have its green shield up. So just letting you know so you can fix it:
The text was updated successfully, but these errors were encountered: