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
"You will need to keep this in mind and do the conversion from EAN-13 to UPC-A yourself. This can be done by removing the front 0 digit from the code to get a UPC-A code."
@JavaLavaMT the issue is actually the opposite: I ask the library to recognize an EAN-13 code but it returns an UPC-A code, which it is not what I asked and it is not what I scanned.
EAN13 codes starting with 0 are detected as UPC-A code, dropping the leading 0 in the returned code.
To Reproduce
Example Steps to reproduce the behavior in sample app:
I have modified the source to print out also the format of the detected code.
Here is the result using an EAN13 starting with 0:
As you can see the detected format is 512, which is UPC-A.
Here is the result using an EAN13 not starting with 0:
The detected format is 32, which is EAN13.
Expected behavior
EAN13 codes should be detected as they are, even when the code starts with 0.
SDK Info:
I'm not sure how to get this info, I simply run
pod install
and this is the result:Smartphone:
Development Environment:
(For Android issue feel free to skip this section)
The text was updated successfully, but these errors were encountered: