discoverReaders throws err after disconnecting a reader

[vivekvardhanadepu]

calling discoverReaders after disconnecting from a reader, throws Could not execute discoverReaders because the SDK is busy with another command: discoverReaders PS: In example-app, you are calling cancelDiscovering on goBack, so, this error is not thrown.

Steps to reproduce:

• discover readers
• connect to a reader
• disconnect reader
• discover readers

Device: any Android 12 emulator

[billfinn-stripe]

Can you please fill out this template? It's the same template you see when you press "New Issue" and then the "Get Started" next to "Bug Report".

**Describe the bug**
A clear and concise description of what the bug is.

**To Reproduce**
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

**Expected behavior**
A clear and concise description of what you expected to happen.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Smartphone (please complete the following information):**

- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]

**Additional context**
Add any other context about the problem here.

[vivekvardhanadepu]

calling discoverReaders after disconnecting from a reader, throws Could not execute discoverReaders because the SDK is busy with another command: discoverReaders PS: In example-app, you are calling cancelDiscovering on goBack, so, this error is not thrown.

Steps to reproduce:

• discover readers
• connect to a reader
• disconnect reader
• discover readers

Device: any Android 12 emulator

Expected behavior on call of discoverReaders, it should give the readers list irrespective of previous event(here, reader disconnection)

[billfinn-stripe]

@vivekvardhanadepu -- what version of the SDK are you using? Note that v0.0.1-beta10 has a fix for a similar-sounding bug: https://github.com/stripe/stripe-terminal-react-native/releases/tag/v0.0.1-beta.10

[billfinn-stripe]

Closing this due to inactivity. Feel free to reopen or create a new issue if your issue has not been addressed.