BarcodeGeneratorView Aztec error

[alex296534]

When upgrading from version 0.5.2 to version 0.7.4, there is a problem when scanning the Aztec code displayed by the BarcodeGeneratorView element on Android. Some mobile barcode reader apps display the correct result, while some do not. It's the same with physical validators. I output a base64 string in the barcode. The error is that the beginning of the line is cut off and some service information is added instead.

<BarcodeGeneratorView Value="{Binding BarcodeValue}" Format="{Binding BarcodeFormat}"/>

[jfversluis]

I think without any additional details about actual data and code that makes this up this is hard to make actionable unfortunately

[alex296534]

I think without any additional details about actual data and code that makes this up this is hard to make actionable unfortunately

I have built a clean maui app with zxing 0.7.4

Added barcode:
<zxing:BarcodeGeneratorView x:Name="barcodeView" Format="Aztec" Value="Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua." HeightRequest="250" WidthRequest="250" />

Installed several barcode reader apps from google play.
Some of them read my barcode wrong:
https://play.google.com/store/apps/details?id=com.idautomation.decoder
https://play.google.com/store/apps/details?id=com.barkoder.demoscanner
https://play.google.com/store/apps/details?id=pl.primesoft.aztecreaderdemo
https://play.google.com/store/apps/details?id=com.gaocang.scanner

They all get something like that instead of lorem ipsum:

HCE20445%81291603614 1?088 16.3
0GKHILJLEACITATGGS6.1333
3=8 0,, ,893 .: ?77. 62,0857 233 4,T[320. ]044.3203614 11&6265660048834 595

HCE20445%81291603614 1?088 16.3
0GKHILJLEACITATGGS6.1333
3=8 0,, ,893 .: ?77. 62,0857 233 4,T[320. ]044.3203614 11&6265660048834 595

EKatbhkAj[ ebgtiacLi#hGKHILJLEACITATGGS6.1333
3=8 0,, ,893 .: ?77. 62,0857 233 4,T[320. ]044.3203614 11&6265660048834 595

In addition, some stationary validators do not read correctly.
I assume that all these applications use some other library (not zxing) to read Aztec.

[DevonHansen]

We had a similar issue, aztec codes are no longer being read by external hardware systems we have no control over, and comparing the old vs the new aztec code it's obvious it's changed (but the data is the same)

I think that may be down to this commit: 422696b#diff-3f98bdb7ac1db11d7652a07511316b352f2ddad9b05ea022f1dcb9a7b1acb289

Was the original character set ISO-8859-1 or has it always been UTF-8?

Did this in a test project now and found ISO-8859-1 isn't the default character set either.

Running ZXing.NET to generate a barcode without the parameters of character set does indeed generate a different Aztec code than what the defaults within ZXing.NET

As a work-around, I set the CharacterSet to null which reverts the Aztec code back to the v0.6.0 image (which was able to be read by external hardware). I couldn't do this with properties given in XAML (or at least I wasn't sure how).

[jfversluis]

Can you try the artifacts from #298?

[DevonHansen]

Re-ran my test project with side-by-side comparison of the three states: default, character set UTF-8 and explicitly setting to null in code-behind.

That fixed the issue as I saw it. Unsure if this solved it for @alex296534 but would be worth a re-run on their side to determine if it works.

[alex296534]

barcodeView.CharacterSet = null; in code-behind solves the problem for all mobile app readers from my list.