You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like the DSB issuing system is countring unicode characters for the U_TLAY instead of raw bytes, crashing the TLB parser in the library. Should we perform a try catch to handle this case?
Example working ticket from DSB with no Unicode:
Example non-working ticket to Copenhagen:
The library crashes at the second one with length=588; index=588
The text was updated successfully, but these errors were encountered:
It seems like the DSB issuing system is countring unicode characters for the U_TLAY instead of raw bytes, crashing the TLB parser in the library. Should we perform a try catch to handle this case?
Example working ticket from DSB with no Unicode:
Example non-working ticket to Copenhagen:
The library crashes at the second one with
length=588; index=588
The text was updated successfully, but these errors were encountered: