Great ANE, but I'm having an issue on Android devices. It's finding the bar code, but reading in a completely incorrect value for it. It works fine with the same code base on every iOS device. Any idea how this could happen? Does the size of the scanning area affects its clarity or understanding of the bar code at all?
For anyone coming across this at a later time, we ended up having to use Symbology.ALL for the scanner config on Android, even though a smaller subset worked fine on iOS.
Great ANE, but I'm having an issue on Android devices. It's finding the bar code, but reading in a completely incorrect value for it. It works fine with the same code base on every iOS device. Any idea how this could happen? Does the size of the scanning area affects its clarity or understanding of the bar code at all?