2.4.3 DigiKey barcode scanning issues about binner HOT 7 CLOSED

The problem seems to be solved in 2.5.0.

from binner.

More diagnostic info:

from binner.

neat, that's a lot of zero's in that barcode. Can you send me a pic of the barcode so I can try to reproduce?

The invalid image token issue can be fixed by logging out then logging in again. I don't know if I've permanently fixed that with 2.4.3 or not, I'll find out today. When your security token gets renewed the images token is supposed to be renewed at the same time but I have seen this before.

from binner.

Given the sequence of loading the newest version was the same as all of the other times I upgraded, I am not sure how it could have been anything other than the correct version but I can't say it definitely was. Since I am running now it doesn't seem that you need to do anything about that at the moment.

The lots o' zeroes barcode:

from binner.

I've added some new configuration so we can have barcode scanner configurations now (basics to start) so we can tweak mostly the rate at which data is buffered. I'm working through a bunch of testing on this right now to see if I can get to the cause of what you're seeing - which I suspect is a difference in key rate. Trying to get this done for today's release

from binner.

I've never used barcode scanning, but I also get the "Invalid Image Token" error in the top right corner with all the parts I have in my database as well as if I click to add a part and it matches to one on DigiKey. I was curious about that one too...

Edit: I re-read your note that this requires logout and login. I tried that, and sure enough it works.

Here's the steps I did today:

1. Was running an old build from ~December
2. Upgraded to 2.4.3
3. Logged in
4. Noticed this issue just now
5. Log out/log in, all is good

This is how the image shows up for an item in my database, not sure if it's right or not?

from binner.

Yup the image token issue is fixed in the current release I'm working on

from binner.