Zxing.net.mobile: iOS plethra of logged messages (Too soon between frames)
Not so much a problem - just curious why we get 24 logged lines (per second) until an image is scanned? Just a sample below;
2020-04-24 14:11:09.707 TestScanQR.iOS[5982:5718857] Too soon between frames
2020-04-24 14:11:09.719 TestScanQR.iOS[5982:5718671] Too soon between frames
2020-04-24 14:11:09.756 TestScanQR.iOS[5982:5718671] Too soon between frames
2020-04-24 14:11:09.828 TestScanQR.iOS[5982:5718671] Too soon between frames
2020-04-24 14:11:09.854 TestScanQR.iOS[5982:5718671] Too soon between frames
Jenni
vmsJenni
All 2 comments
Having the same problem, and I've used the workaround described in https://github.com/Redth/ZXing.Net.Mobile/issues/721 by setting the DelayBetweenAnalyzingFrames and DelayBetweenContinuousScans to 20 (5 was needlessly short) which removes the logging but increases CPU utilization.
I've reproduced this issue on both version 2.4.1 and 3.0.0-beta5, and on a variety of apple devices (running iOS 12.0.1, iOS 13.5.1 and iPad OS 13.5.1). Our implementation is using the basic ZXingScannerPage with options TryHarder, AutoRotate, TryInverted set to false and QR as the only possible format.
henziger
on 6 Jul 2020
Same here.
mduchev
on 6 Jul 2020
Related issues
PaulVrugt
路
3Comments
sushibear
路
6Comments
SansDK
路
6Comments
TobioDev
路
4Comments
roelvdwater
路
6Comments
Most helpful comment
Having the same problem, and I've used the workaround described in https://github.com/Redth/ZXing.Net.Mobile/issues/721 by setting the DelayBetweenAnalyzingFrames and DelayBetweenContinuousScans to 20 (5 was needlessly short) which removes the logging but increases CPU utilization.
I've reproduced this issue on both version 2.4.1 and 3.0.0-beta5, and on a variety of apple devices (running iOS 12.0.1, iOS 13.5.1 and iPad OS 13.5.1). Our implementation is using the basic ZXingScannerPage with options TryHarder, AutoRotate, TryInverted set to false and QR as the only possible format.