#Catima 2.41.3 is out

github.com/CatimaLoyalty/Andro…

This builds on the hotfix in 2.41.2 to also fix .pkpass files explicitly stating ISO-8859-1 as format.

It also forcibly sets the barcode format of all existing cards to ISO-8859-1 on upgrade. This used to be the only format supported in Catima, so this reverts any sudden barcode changes.

We may need another bugfix release to get this all right. If you understand UTF-8, *please* join in in github.com/CatimaLoyalty/Andro….

in reply to Sylvia

Those of you who use the #Deutschlandticket are likely affected in 2.41.0 - 2.41.2. And scanning a Deutschlandticket with your camera or from a PDF file (not using a .pkpass file) will likely not work correctly.

The current workaround for both cases is to manually set the "Barcode encoding" field in the card setting to "ISO-8859-1".

Not currently sure how to fix scanning Deutschlandtickets with the camera without breaking the issue 2.41.0 was meant to fix by adding barcode encoding support :(

in reply to Sylvia

I decided to just quickly release 2.41.4 and disable the automatic barcode encoding detection for now. Breaking Deutschlandticket is definitely one of the worst things that could have happened and I don't want people to get stranded in Germany.

github.com/CatimaLoyalty/Andro…

I've asked @IzzyOnDroid and linsui (from @fdroidorg) to get this release out more quickly if possible: github.com/CatimaLoyalty/Andro…

Coming soon to an app store near you.

#IzzyOnDroid #FDroid #GitHub #GooglePlay

in reply to 🍐Penglix🍐

Yes, from 2.41.0 - 2.41.3 Deutschlandticket is fully unusable based on the information I have. This includes Deutschlandtickets added to Catima before 2.41.0

In 2.41.4 both pkpass and scanned with camera Deutschlandtickets should work again as they did in 2.40.X and existing tickets will be fixed on installing the update with no user intervention needed.

Edit: 2.41.3 should deal with the pkpass correctly already, but 2.41.4 will fix also non-pkpass

This entry was edited (1 day ago)