You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
During continuous scanning if you pause after scanning a particular qrcode, then after resume scanning you rescan the same code the promise/scan result doesn't retrigger. If you scan a different qrcode it acts as it should and retriggers after each new scan.
To Reproduce
Steps to reproduce the behavior:
Use continuous scanning
get results and pause
resume scanning after user action, such as closing an alert
scan same code again, unsuccessful no ScanResult is resolved
Expected behavior
After resuming scanning any successful scan should trigger the scanResult promise, during continuous scanning, even repeats.
Screenshots
From the image between the resumeScanning and the startScanning result I tried to rescan the same code, but until I switched to a new code it wouldn't work. This continues to the next where basically the only way to retrigger the scanResult is to alternate and not repeat scanning the same code.
Version
v2.1.0
Smartphone (please complete the following information):
Device: OnePlus 7T
OS: Android 11: Oxygen OS 11.0.6.1.GM21AA
Browser: native app
Version: Capacitor 3.3.2
Additional context
My suggested solution would to be allow a property to be set in ScanOptions to allowRepeatCodes, or to just use the expected behavior listed above as default behavior.
The text was updated successfully, but these errors were encountered:
JEVietti
changed the title
ResumeScanning doesn't retrigger startScanning result
Duplicate QR Code doesn't resolve during Continuous Scanning
Apr 19, 2022
Describe the bug
During continuous scanning if you pause after scanning a particular qrcode, then after resume scanning you rescan the same code the promise/scan result doesn't retrigger. If you scan a different qrcode it acts as it should and retriggers after each new scan.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
After resuming scanning any successful scan should trigger the scanResult promise, during continuous scanning, even repeats.
Screenshots
From the image between the resumeScanning and the startScanning result I tried to rescan the same code, but until I switched to a new code it wouldn't work. This continues to the next where basically the only way to retrigger the scanResult is to alternate and not repeat scanning the same code.
Version
v2.1.0
Smartphone (please complete the following information):
Additional context
My suggested solution would to be allow a property to be set in ScanOptions to allowRepeatCodes, or to just use the expected behavior listed above as default behavior.
The text was updated successfully, but these errors were encountered: