|
Or could it be that your app's target framework in the Info.plist is still at iOS 5.x?
Just an idea, although the screenshot states 6.1 in the top left corner.
wrote:
Rick,
as the didUpdateName method is also missing in your screenshot:
maybe an Xcode bug? :-)
Etan
wrote:
Wow. I looked for that using the method popup, and didn't see it, which lead me to believe you were speculating about the name.
Proof:
<Screen Shot 2013-04-19 at 14.55.33 .png>
On Apr 19, 2013, at 14:25 , Etan Kissling < email@hidden> wrote:
Rick,
the accessory cannot respond to indications, but has to send them ;-)
iOS does the job on the remote side, so it receives the indication when
it is connected and your accessories emits the indication.
The callback is in CBPeripheralDelegate:
/*!
* @method peripheralDidInvalidateServices:
*
* @param peripheral
The peripheral providing this update.
*
* @discussion
This method is invoked when the @link services @/link of <i>peripheral</i> have been changed. At this point,
* all existing <code>CBService</code> objects are invalidated. Services can be re-discovered via @link discoverServices: @/link.
*/
- (void)peripheralDidInvalidateServices:(CBPeripheral *)peripheral NS_AVAILABLE(NA, 6_0);
On 19.04.2013, at 23:07, Rick Mann <email@hidden>
wrote:
On Apr 19, 2013, at 02:36 , Etan Kissling <email@hidden> wrote:
Excerpt from https://developer.apple.com/hardwaredrivers/BluetoothDesignGuidelines.pdf
The iOS device implements the GAP Service Changed characteristic, because the database contents can change at any time. The Bluetooth accessory should therefore support the Characteristic Value Indication of this characteristic and, upon receiving indications, invalidate
its database cache accordingly. See the Bluetooth 4.0 specification, Volume 3, Part G, Section 7.1.
Hmm. That excerpt seems to say that the *accessory* needs to respond to the indication by invalidating its own caches, rather than saying iOS will do the same thing.
Did not test this, but if it works, you should get a callback in the CBPeripheralDelegate (didInvalidateServices or something similar).
So, there's no such delegate method, but I think the thing to do is get the value change indication for that specific characteristic. I'll try to implement that, and hopefully the caching won't prevent that characteristic from showing up.
Actually, huh. I only change the service when I flash the BLE112, so I don't know how to properly send the update, without sending it every time the thing boots.
--
Rick
--
Rick
|