nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Invalid barcodes scanned on Android 25.2.3

NicolasGIS

Hello,

Since our workers migrated to Field Maps 25.2.3 on android, barcodes are not properly scanned.

The very same barcode is decoded with different values each time it is scanned. Here are few examples from 10 different scans in a row of the same barcode:

The barcode looks like the following:

So 5117 is the correct value.

Reproducible on multiple android devices. My example was done with a Galaxy Tab S9 fairly recent.

On IOS, the same barcode is properly decoded on IOS.

Anybody facing the same issue ?

Thanks,

Best regards,

Nicolas

Najděte více příspěvků označených jako

Accepted answers

NicolasGIS

Hi @ChrisDunn1,

Thanks for your quick reply: much appreciated.

Support was easily able to reproduce and logged the following BUG:

BUG-000182225 - Field Maps barcode scanning returns incorrect results for Code-39 on Androids.

I already escaladated it as it's a big issue for us.

Thanks

All comments

NicolasGIS

Hi @ChrisDunn1,

Thanks for your quick reply: much appreciated.

Support was easily able to reproduce and logged the following BUG:

BUG-000182225 - Field Maps barcode scanning returns incorrect results for Code-39 on Androids.

I already escaladated it as it's a big issue for us.

Thanks

ChrisDunn1

Hi @NicolasGIS ,

Thanks for reaching out - I'm sorry this is causing issues. Unfortunately we don't have any updates on our end. You are correct that the best next step is to log a bug through support so they can investigate as well, that will help us assess and prioritize the issue and/or determine if there's something else that can be done.

Chris

NicolasGIS

Hello @ChrisDunn1,

Any update on this issue ? Our workers are losing a lot of time on the field because of this issue as they have to scan many times the same barcode to get the proper value.

Another complain from them is that the scanning area (rectangle) is much smaller than it used to be making it even more difficult to scan not easily accessible bar code.

To put it in a nutshell, Field maps > 25.2 generated a big decrease of productivity and dissatisfaction from our workers. I keep saying it will be fixed at some point but as they are using it on a daily basis, it generates a lot of frustration.

What would you recommand ? Should an official BUG be logged ? Is it maybe already the case ?

Thanks

NicolasGIS

Well, unfortunately, it is not possible. We have thousands of those spread around all the campus 😕

ChrisDunn1

Thanks for sharing that @NicolasGIS, I'll pass it along to our developers as well. Given that this may be an underlying issue that we can't do much about, how feasible is it for you to reprint barcodes using a different encoding? Ultimately that may be a quicker solution unfortunately.

NicolasGIS

FYI @ChrisDunn1, there is also a more official android BUG related to Code-39:

https://issuetracker.google.com/issues/342003174

I guess it is not a good piece of news...

ChrisDunn1

Thanks @NicolasGIS - that is super helpful. I'll pass this information onto the developers.

NicolasGIS

Hi @ChrisDunn1,

Just found also this thread that looks very similar to our issue:

https://github.com/mrousavy/react-native-vision-camera/issues/2593

And it is also code-39 ...

NicolasGIS

Hi @ChrisDunn1,

According to them this is Code-39. I kind of confirm it with an external barcode generator:

https://barcode.tec-it.com/en/Code39?data=*5117*

VS original bar code:

They look pretty much the same.

With the first bar code generated from the website above, I can reproduce the issue of ArcGIS Fields Maps not properly decoded it though it happens less often.

Does it help ?

Thanks,

Nicolas

ChrisDunn1

The types of encoding might be something like Code-128, Code-39, Code-39 Full ASCII, MSI. If the people who created them aren't sure of the encoding, even knowing the tool that was used (an online generator, python, etc) would likely help.

NicolasGIS

Hi @ChrisDunn1,

Thanks for having a look ! Much appreciated.

We are having this issue with all our barcodes that look more or less the same as the one I posted. This is the reason why this issue is quite annoying.

Regarding the encoding I don't know. I can ask. What are the typical encodings protocol ? Just to give them an example of what you expect ?

Thanks,

Nicolas

ChrisDunn1

Hi @NicolasGIS ,

I can reproduce the issue with the barcode that you shared, though it doesn't happen with any others that I create. Are you seeing the problem on a lot of different barcodes or just this one?

Also, do you know the type of encoding used for the barcode? I tried to recreate a fresh version with the same value but none of the encoding options I used looked exactly the same.

Chris

Připojte se k diskusi

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.