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.

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

Closed
mpedersen15 opened this issue Feb 24, 2015 · 5 comments
Closed

isDiscovered returns null after reconnect #141

mpedersen15 opened this issue Feb 24, 2015 · 5 comments
Labels

Comments

@mpedersen15
Copy link

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!

@randdusing
Copy link
Owner

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.

@randdusing
Copy link
Owner

Oops forgot iOS discovery works much differently and this shouldn't be possible on iOS. Was your original bug report was only for Android?

@mpedersen15
Copy link
Author

Yep you're correct, only for Android. iOS has been working pretty consistently for me! Thanks for checking this out!

@randdusing randdusing added the bug label Feb 26, 2015
@randdusing
Copy link
Owner

Should be good to go now.

@mpedersen15
Copy link
Author

Awesome thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants