We noticed that in older OS versions the accessory picker would consistently display a peripheral's advertised friendly name on top of displaying information from the matching display item. While in newer OS versions we would mostly only see the name from the display item. Is there a way to configure this?
AccessorySetupKit will read the name advertised by the accessory to display the information in the accessory picker. If that is missing, we will not be able to display that information. Can you confirm if the accessory always has a valid name in its advertising info (either ADV_IND or SCAN_RSP) ?
Would this be the same name we would expect to see under CBAdvertisementDataLocalNameKey in the BLE advertising data?
One thing that I just now noticed when scanning using core bluetooth without ASK is that the very first peripheral discovery event is always missing the CBAdvertisementDataLocalNameKey field in the ad data, with subsequent discovery events having name. Would this behavior affect how ASK behaves?
Hello. This is expected behavior if you put the name AD type in the accessory SCAN_RSP and not in the ADV_IND. CoreBluetooth API will report each event separately by order, and we aggregate that info into the same dictionary reported to the client.
Ok. But does that behavior affect how ASK behaves? Are you saying that our products need to put the name AD type in ADV_IND in order to work correctly with AccessorySetupKit?
as for how this behavior would affect ASK, would you be able to file a feedback of your device setting up your accessory with ASK so we can track this and fix any potential issue we see? Thank you!
Sure thing. I can do that. What kind of info would be helpful for you guys with that feedback request?
Just for reference. This is generally what we're seeing from the accessory picker with one of our products. We never usually see the advertised friendly name with any accessories shown. It's there sometimes, but very seldomly. This is also leading to issues showing multiple products advertising at the same time which I posted as a separate question within this thread.
