mobile_scanner 7.1.2 returns EAN-13 for UPC-A bar codes

[jorgenpt]

I have only tested this on iOS, but after upgrading to 7.1.2 from 6.0.2, UPC-A barcodes are scanning as EAN-13 with a leading zero, where 6.0.2 did not. This means that lookups between versions no longer match. I’ve attached a photo of a bar code that exhibits this behavior.

I didn’t see anything about this in the breaking changes for 7.0 or 7.1, is this expected?

[navaronbracke]

Version 7 uses the Vision API on iOS, so maybe that's an issue with the Vision API.

[jorgenpt]

My workaround is simply to always treat 12 digit EAN-13 barcodes (I.e. with a 0 prefix) as UPC-A barcode — I don’t know if that’s a change that’s appropriate to put directly in mobile_scanner? I don’t think there’s a good way to distinguish between an actual EAN-13 with a zero suffix and a UPC-A code.

[navaronbracke]

Does this happen with MLKit on Android? Or is it iOS specific?

[jorgenpt]

I did not have a convenient device to reproduce the issue on Android, so I just blanket applied the workaround on both platforms. Seems better to have a unified result across both of them either way. But I might be able to roll back and test on Android if needed.