-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to parse QR code
error hangs
#334
Comments
I have indeed the same issue when I follow your steps to reproduce.Interestingly I don't have a problem when between step 1. and 2. I close the error message. Is that the same for you? |
you're right, its the same for me. |
anyway error messages should dissappear after an x amount of time i think. |
Errors disappear automatically in "regular mode" (non-dev). I agree they shouldn't be truncated in dev mode, but in regular mode the user usually does not care about any technical details. Just if it was their fault or some technical error. We need to improve the error experience, no doubt. @Oran-Dan It could make sense to also provoke errors in regular mode (dev mode disabled) to complete the picture and collect more UX feedback. 👍 |
Failed to parse QR
error hangs
Failed to parse QR
error hangsUnable to parse QR code
error hangs
Description
After scanning a qr code which fails, all subsequent scans display the same error with the qrcode text from the original error. So the error message stays the same even though the qr code has changed to one which would otherwise always work, if it hadnt been for the error prior to that.
Sometimes it seems to escape this loop, but especially on a fresh profile with the first scan being a failed one, the error seems to hang indefinitely.
Hardware Specification
Operating system:iOS
RAM:
Cores:
Device: iphone
Steps to Reproduce the Bug
Actual Behaviour
error hangs
Expected Behaviour
error doesnt hang and every new scan should work fine after the first failed.
Errors
error: failed to parse QR code
The text was updated successfully, but these errors were encountered: