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
According to this issue comment, "this application will not be able to support GS1_128 barcodes" (as zxing is currently unable to generate this type).
I have a (UK-issued) Nectar card and when I scan the card using "Capture card", the generated barcode does not match the barcode on my Nectar card. Comparing the 2 images to those created by online barcode generator websites, it appears as though loyalty-card-locker is creating a "Code-128" barcode while the real (scanned) card is a "GS1-128 (UCC/EAN-128)" barcode.
Is there any way round this? Many thanks.
(The next time that I'm in store, I'll see whether any of the other barcodes shown under "Edit card" work. Hopefully, I won't arouse suspicion by futzing with their checkout machine for 10 minutes! 😆😆😆)
According to this issue comment, "this application will not be able to support GS1_128 barcodes" (as zxing is currently unable to generate this type).
I have a (UK-issued) Nectar card and when I scan the card using "Capture card", the generated barcode does not match the barcode on my Nectar card. Comparing the 2 images to those created by online barcode generator websites, it appears as though loyalty-card-locker is creating a "Code-128" barcode while the real (scanned) card is a "GS1-128 (UCC/EAN-128)" barcode.
Is there any way round this? Many thanks.
(The next time that I'm in store, I'll see whether any of the other barcodes shown under "Edit card" work. Hopefully, I won't arouse suspicion by futzing with their checkout machine for 10 minutes! 😆😆😆)
edit: I've just found https://stackoverflow.com/a/34538369/3499840 ("ZXing does support GS1-128...")
The text was updated successfully, but these errors were encountered: