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
Hello,
In France it is possible to send letters using stamps with a qRcode allowing the letter to be tracked. But I noticed that on my sending yesterday barcode misdetected the qrcode and generated an error on the last digit of the character string. I kept an image of this qrCode via the application but the green crosses at each end prevent me from scanning the qrCode again. But when I dropped off my letter at the Post Office, I asked the employee to scan the qRcode. It came out correctly.
You can see at the end that BarCode read ...479333 or it is a .....479337. 0r you have an extra 3 :-(
(sorry, my english is note very fluent and i used a translation tool. Also, i'm not a developper and my experience in github is very recent)
Thanks a lot
The text was updated successfully, but these errors were encountered:
That's an interesting case. So far two barcode readers that I found for Android produced the same result as mine, i.e. with ...479333... I'll try to debug this issue when I have time. And thanks for reporting it!
Hello,
In France it is possible to send letters using stamps with a qRcode allowing the letter to be tracked. But I noticed that on my sending yesterday barcode misdetected the qrcode and generated an error on the last digit of the character string. I kept an image of this qrCode via the application but the green crosses at each end prevent me from scanning the qrCode again. But when I dropped off my letter at the Post Office, I asked the employee to scan the qRcode. It came out correctly.
You can see at the end that BarCode read ...479333 or it is a .....479337. 0r you have an extra 3 :-(
(sorry, my english is note very fluent and i used a translation tool. Also, i'm not a developper and my experience in github is very recent)
Thanks a lot
The text was updated successfully, but these errors were encountered: