Description
Describe the bug
There's a state when the reader was found by the app, and the app asks for user confirmation before connecting to a specific reader:
During this, the reader might become powered off. If the user still taps Connect to reader
after this, the app will try to connect to the reader, for approximately 45 seconds, before saying it can't connect.
But there's a chance that user will not wait for 45 seconds, and will tap Cancel
. Here lies the issue - it looks like the app will still try to connect to the same reader in all subsequent attempts, unless the app is relaunched. Only after that, the app will show the expected Scanning for readers
window. An example is in the video below:
IMG_5880.MOV
To Reproduce
- Power on the reader
- Open
Settings
~> IPP ~> Manage Card Reader and tapConnect card reader
- Once the app asks if you'd like to connect to the found reader, power off the reader
- Tap
Connect to reader
- Make sure the app tries to connect to the reader, and tap
Cancel
- Try reconnecting again ~> it looks like the app will still try to connect to the same reader, instead of staring the process from scratch.
Expected behavior
I'd expect the app to show the Scanning for readers
window after new connection attempt in step 6.
Isolating the problem (mark completed items with an [x]):
- This bug happens with a default WordPress theme active, or Storefront.
- I can reproduce this bug consistently using the steps above.