-
Notifications
You must be signed in to change notification settings - Fork 70
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
iOS setNotifiable custom service/char #157
Comments
Also getting this error on iOS. |
@nick-craffey I haven't gotten around to testing it yet or dive into documentation but I was using another library quick_blue_plus and I had to "discover services" for the services to actually be populated within a Bluetooth object, then I could perform writes/reads/setNotifiable. So this library might need the same thing. Although last time I checked, that call in this library isn't |
So my above hypothesis was correct. You first have to discoverServices (for me - after connecting) and then you're able to successfully set Some updated documentation would be helpful to know that. Maybe it's common BLE knoweldge. Another recommended update would be to make this functions discover all services/characteristics and have it be async. I had to wait for when the service/characteristic I needed popped up in the handler This specific issue can be closed when the author of the repo sees it, but I would recommend one or both of the above as an enhancement to this repo |
Hello,
I can't seem to subscribe/setNotifiable custom service/characteristics
I'm trying to subscribe to a custom service's characteristic but getting a
nil
error when callingsetNotifiable
I see in the Swift code the id has to have been in the services array or be formatted for more general characteristics (like battery) but that array is showing up as empty. Where do the service Ids and characteristic Ids get set before calling
setNotifiable
and is this needed?Swift error location:
Test Device:
iPad (6th generation) 15.3.1
Development Device:
Mac M1 Pro
The text was updated successfully, but these errors were encountered: