Detecting of wrong barcode number

[Kancheraj]

detecting the number as 041570121627, but it should be returning 0041570121627—it’s dropping the initial zero.

[navaronbracke]

What version of mobile_scanner are you using? What platform are you seeing this on?

If this is on Android, then it looks to be an MLKit bug, which we cannot really fix ourselves.

[Kancheraj]

What version of mobile_scanner are you using? What platform are you seeing this on?

If this is on Android, then it looks to be an MLKit bug, which we cannot really fix ourselves.

mobile_scanner: ^6.0.2 both device android and ios

[Kancheraj]

any update on this ?

[navaronbracke]

We moved away from MLKit for iOS in the new beta for version 7.0.0, you could try this with version 7.0.0-beta.3.

For Android, we depend entirely on updates in https://developers.google.com/ml-kit/release-notes

I see that for the bundled model, we use version 17.2.0, while there is a 17.3.0 available.
https://mvnrepository.com/artifact/com.google.mlkit/barcode-scanning/17.3.0

I'll try to bump this for the next beta release, but otherwise there is not much we can do.

[softak098]

This is an US EAN-13 code and problem is the initial zero.

Most scanners, even hardware one recognizes EAN-13 code with initial 0 as an UPC-A code,
efectivelly removing the first number and returning only 12 characters (because by default in UPC-A initial 0 is hidden).

If the MLkit does not have parameter to include country code for UPC-A (the initial zero) and return 13 characters, you have limited options to check such situation.