RE: Cannot connect to peripheral using custom vendor service (nAN-36)

Scott — Tue, 22 Jul 2014 02:30:46 GMT

I was also bitten by this "feature". Since it's no longer obvious how to clear the cache in OSX, the steps are:

sudo defaults write /Library/Preferences/com.apple.Bluetooth CoreBluetoothCache -dict
sudo launchctl unload /System/Library/LaunchDaemons/com.apple.blued.plist
sudo launchctl load /System/Library/LaunchDaemons/com.apple.blued.plist

Also be warned if you are using the ble_app_hrs example to create your own custom UUIDs you need to make sure you call services_init() before advertising_init() in the main function. Otherwise your custom UUID is not yet initialised.

RE: Cannot connect to peripheral using custom vendor service (nAN-36)

Samuele Forconi — Fri, 21 Feb 2014 18:31:39 GMT

Solved. It was Core Bluetooth Framework that caches previous characteristics and pairing status. Cleaning the cache (from Settings Panel), solved the problem. Now, I can successfully see the Led Service.

Sorry for the useless post.