Scan never ends
See original GitHub issueIf I use scanPath
or scanBytes
to scan an image, and the image doesn’t have a barcode, the code keeps waiting instead of returning null
or throwing an exception or anything like it.
For example:
String path = '/path/to/my/image.jpg';
print('scanning barcode...');
String barcode = await scanner.scanPath(path);
print('done');
Will print “done” only if the image has a barcode. If not, “done” will never get executed and the code will keep on waiting to scanner.scanPath
to finish. No exceptions are thrown.
- Tested on an Android device
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Defender scan never finishes windows 10s mode
I have never been able to run a defender scan. When I click quick scan, it shows dots like it is scanning but...
Read more >What to do when a Tenable.io Web Application Scanning scan ...
What to do when a Tenable.io Web Application Scanning scan never finishes or times out. Tenable recommends that you first run high-level overview...
Read more >Scan never finishes - Malwarebytes for Windows Support Forum
My Malwarebytes won't stop scanning after reaching the "Scanning File System" stage. It's gone as long as 70 hours once before I had...
Read more >Windows 10: quick scan never completes
When I try to employ a "Quick Scan" procedure in Defender, the scan progress indicator, coloured green, stops half way and does not...
Read more >Bitdefender Scan Never Finishes.
Bitdefender Scan Never Finishes. ... The scan can end after the infected files are moved to quarantine, deleted or ignored.
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 FreeTop 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
Top GitHub Comments
Folks, i made a pull request to allow catching this error. Check this out #92 😃
Not really. As a workaround you can set timeout for the future method:
and you should catch the timeout exception, or pass
onTimeout
argument totimeout
method.