-
Notifications
You must be signed in to change notification settings - Fork 354
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
isDiscovered returns null after reconnect #141
Comments
Thanks for the bug report. I've found the issue on Android and should be very similar on iOS. I should be wrapping up the next version tonight. |
Oops forgot iOS discovery works much differently and this shouldn't be possible on iOS. Was your original bug report was only for Android? |
Yep you're correct, only for Android. iOS has been working pretty consistently for me! Thanks for checking this out! |
Should be good to go now. |
Awesome thanks! |
Hi Rand,
I'm working on creating some robustness when connecting to my BLE peripheral, and want to make sure I can reconnect and then write to the device after it gets disconnected. The isDiscovered function works perfectly after the initial connection to the peripheral, but after I reconnect successfully, isDiscovered only seems to return null. Could this be a bug of some kind?
Thanks for the help and the great plugin!
EDIT: This problem only exists on Android, since iOS has a different procedure for service and characteristic discover!
The text was updated successfully, but these errors were encountered: