Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Scanning only starts after second call if bluetooth state is not observed #143

Open
lettoka opened this issue Sep 5, 2024 · 0 comments
Open

Scanning only starts after second call if bluetooth state is not observed #143

lettoka opened this issue Sep 5, 2024 · 0 comments

Comments

@lettoka
Copy link

lettoka commented Sep 5, 2024

Hi!

I had a problem only happening on iOS that I have to call startScan twice to actually start scanning. I spent some time debugging, and comparing my implementation to the example project. After listening to the adapterState and only start scanning after this, solved the issue. I don't know if it's a bug, but I thought I would share this information.

My version is: 1.32.12

Thank you for the amazing library!
Cheers,
Levi
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lettoka