mastodon - Link to source

#Catima 2.39.1 is out!

github.com/CatimaLoyalty/Andro…

This fixes a crash bug which was reported using the new #ACRA crash reporter functionality *less than 3 hours after the last version released*. If that's not an ACRA success story I don't know what is ;)

Coming soon to an app store near you!

#IzzyOnDroid #GitHub #FDroid #GooglePlay


Release 2.39.1 · CatimaLoyalty/Android

Fix possible crash that could occur for cards missing colour information in the database
GitHub
#fdroid #github #googleplay #catima #izzyondroid #acra
in reply to Sylvia

mastodon - Link to source

Sylvia

For those curious the fixed bug is github.com/CatimaLoyalty/Andro…. ACRA delivered a very clear stack trace and other information like the Android version which helped to triage this quickly.

Interestingly enough, this code that crashed seems to have been around for *8 years*, a very simple off-by-one error. Due to a series of circumstances, the user ended up with a card with no header colour.

When picking a header colour, the name of the card was used and modulus 8 was done on it. However...


Crash in LetterBitmap.pickColor

Just reported with our brand new crash reporter. Thanks ACRA, didn't expect you to come in handy this quickly. OnePlus 13 (CPH2653), Android 15. User reported the crash happening the moment they ta...
TheLastProject (GitHub)
in reply to Sylvia

mastodon - Link to source

Sylvia

Given there were only 7 valid colours, that means there was a 1 in 8 chance of picking an invalid colour, causing a crash.

The most surprising part, to me, is not the bug. It's a very simple mistake to make. What does surprise me though is that a crash issue in 8 year old code never got reported before.

This is yet another reminder that if you're frustrated about something, make sure it's actually reported! The dev may simply not be aware of the issue! :)

⇧