-
Notifications
You must be signed in to change notification settings - Fork 19
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
Discovery doesn’t work (OS X 10.11, iOS 9) #9
Comments
@sander please provide a full debug log. Also, I'm wondering if CoreBluetooth/blued is not reporting the ANCS GATT service anymore in OS X 10.11. Would you be able to get a screenshot from the LightBlue OS X app connected to an iOS 9 peripheral? |
@sander thanks From the logs looks like no services are discovered:
node-ancs is looking for the following service UUID when it discovers services: Here's a screenshot from my OS X 10.10 (Yosemite) Mac connecting to an iOS 9 iPhone: Again, no service UUID |
Thank you @sandeepmistry. I’ve asked about this on the Apple dev forums: ANCS service on iOS 9 not discovered in OS X 10.11 (pending mod approval) This post about Mac/iOS listening to iOS’s ANCS suggests that ANCS may be filtered out indeed in CoreBluetooth. |
The library used to work well between my MacBook and iPhone, but a few months later (with an iOS reinstallation and OS X upgrade in between) it doesn’t. I’m trying it this way:
DEBUG=* node test.js
on OS X.Expected: Node recognizes the phone advertisement (with device name ‘testje’) and displays a sequence ‘discovered’, ‘connected’, ‘services and characteristics discovered’.
Instead: Node just outputs all advertisements it finds, and doesn’t handle the ‘testje’ one differently. No connection etc. See the relevant output lines below:
I’ve tried both with and without the devices being paired using Bluetooth Settings. ANCS from the same phone to Linux works, using https://github.com/robotastic/ble-ancs.
Am I missing a step? Should node-ancs still be working with this combination of OS versions?
The text was updated successfully, but these errors were encountered: