OnScanResult event is not fired
See original GitHub issueI’m just doing my first steps with this but something doesn’t seem to work right here. I’ve integrated the component like this:
<zxing:ZXingScannerView OnScanResult="Scanner_OnScanResult"/>
And I’m getting a picture and all but the event is not raised. However I do see “Barcode Found” messages in the Debug output.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:11 (2 by maintainers)
Top Results From Across the Web
Android BLE onScanResult is never called
So I bought a tablet (Android 9) and there onScanResult is never called, but when I search with Android board-function I see the...
Read more >iOS scanning not working (OnScanResult never fired) #967
Just tried ZXing 3.1.0-beta2 and still doesn't work with iOS. Sees image, but doesn't ever read the qrcode/fire event. Android works fine ...
Read more >ScanCallback | Android Developers
Quickly bring your app to life with less code, using a modern declarative approach to UI, and the simplicity of Kotlin. ... Start...
Read more >ScanCallback.OnScanResult(ScanCallbackType, ...
Determines how this callback was triggered. Could be one of ScanSettings#CALLBACK_TYPE_ALL_MATCHES , ScanSettings#CALLBACK_TYPE_FIRST_MATCH or ScanSettings# ...
Read more >Bluetooth Android Plugin Problem
The only thing I noticed is that 'onScanResult' function runs in a different thread than 'scanLeDevice'. Is that causing the problem?
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I can… it’s just, I don’t have the issue anymore and I don’t know if I can reproduce it.
Still, testing with v3.x would be helpful; maybe the bug is easier to be reproduced in this version.