Reproducible Build for v1.1.3 failed

[IzzySoft]

was easy to fix, luckily – but please, take a look at our RB Hints for Developers, and especially at the "first basic rule" there. You've tagged a release, then changed versioning, then built, and only then committed the changes – that broke the neck, as built from the tagged commit, we get a different version.

TL;DR: Please "always build the release APK from a clean tree at the commit the release tag points to" 😉

We had to apply a dirty hack to make this release RB – which means, the next release will automatically fail as well until we manually remove that hack again 🙈

git checkout cadea70ff5ed1f35ed89c654b55acbff82a867f2      # the commit holding your changes
git reset --soft 6eba214ef72caf7ac135df206c386316b31cb36d  # the commit the APK claims to have been built from
./gradlew assembleRelease

Thanks for taking care! 🤗

--- END BUILD LOG ---
Keeping '5ff29e9ad07d5dcefd6e06424c4e9c969e653b70871c60a9b4e08728b073c049-compress.joshattic.us-1.1.3-upstream.apk'...
Keeping '290173bac2336fa0dc09dd626204fd723fd103ff3f1a38ef6c2d40a0ca887108-compress.joshattic.us-1.1.3-unsigned.apk'...
Reproducible: True

[JoshAtticus]

Apologies! I built and uploaded the APK but forgot to push my commits!

[IzzySoft]

And tagged the wrong commit 🙈 Well, 💩 happens. And life is constant learning 😉

[JoshAtticus]

GitHub automatically tags commits, I don't think it allows me to change them

[IzzySoft]

First time I hear that. Back in the time when I used Github (moved my stuff to Codeberg long ago), I created my tags and releases myself: git tag to create a tag, git push --tags to push them to Github, and then the Github WebUI to create a release (which let me pick a tag or commit for that) Looks like it still works the same way today 😉

Well, we'll find out with the next release. Maybe you just hit some "glitch".

[IzzySoft]

Was just about to complain v1.2.0 failed RB. Then I got confused about the commit it was built from. Took me a little to remember our issues here from last time 🙈 Our framework cleaned up the git checkout we had to add, but left in the git reset, which was to be expected (I told ya) 🤪

So give Atticus a snack from me: after cleaning up the remains from our "ugly hack" last time, this release worked out fine again 🤗 Thanks!

[IzzySoft]

TL;DR: Please "always build the release APK from a clean tree at the commit the release tag points to" 😉

❗ ❗ ❗ ❗ ❗

I'd use a bigger font would the editor offer it. Again. You've built the APK from the commit FOLLOWING the tagged one – a sure way to break RB (and the diff of classes2.dex was rather huge). But when building from the commit the APK has embedded, the build fails entirely:

> Task :app:compileReleaseKotlin FAILED                                                                                                                        
e: file:///build/repo/app/src/main/java/compress/joshattic/us/CompressorViewModel.kt:79:41 Syntax error: Expecting '"'.                                        
e: file:///build/repo/app/src/main/java/compress/joshattic/us/CompressorViewModel.kt:79:41 Syntax error: Expecting comma or ')'.                               
e: file:///build/repo/app/src/main/java/compress/joshattic/us/CompressorViewModel.kt:79:41 Syntax error: Incorrect template entry: .                           

So you must have had local, uncommitted changes in the tree as well when building – and those are still not committed / pushed, as there is no newer commit available here.

• Tagged: 588d0c1
• embedded in the APK: 502b1d1

Passing this release as "RB failed" now. Please, please take more care with the following release(s) 🙏

[JoshAtticus]

TL;DR: Please "always build the release APK from a clean tree at the commit the release tag points to" 😉

❗ ❗ ❗ ❗ ❗

I'd use a bigger font would the editor offer it. Again. You've built the APK from the commit FOLLOWING the tagged one – a sure way to break RB (and the diff of classes2.dex was rather huge). But when building from the commit the APK has embedded, the build fails entirely:

> Task :app:compileReleaseKotlin FAILED                                                                                                                        
e: file:///build/repo/app/src/main/java/compress/joshattic/us/CompressorViewModel.kt:79:41 Syntax error: Expecting '"'.                                        
e: file:///build/repo/app/src/main/java/compress/joshattic/us/CompressorViewModel.kt:79:41 Syntax error: Expecting comma or ')'.                               
e: file:///build/repo/app/src/main/java/compress/joshattic/us/CompressorViewModel.kt:79:41 Syntax error: Incorrect template entry: .                           

So you must have had local, uncommitted changes in the tree as well when building – and those are still not committed / pushed, as there is no newer commit available here.

• Tagged: 588d0c1
• embedded in the APK: 502b1d1

Passing this release as "RB failed" now. Please, please take more care with the following release(s) 🙏

Sorry I'm kind of burnt out and accidentally uploaded the wrong apk file. I was trying to get the release out fast so I could go relax. I'll try not to do it again.

you can also put a hashtag in front of your text for really big text

[IzzySoft]

Most serious mistakes happen when in a rush 🙈 And yeah, I know about the hash tag. I usually avoid that, as it is different from BIG TEXT as it messes with the page structure (being converted into a header – here, a top-level <h1> even). But I can use an Alert like

Caution

Be more careful next time, please! Rushing things is calling for bugs 🐛

next time, if you want 😉 Though it might be much preferable I would not need that, as there would be no "next time with this" 🤪