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.

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?

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?

Would this be the same name we would expect to see under CBAdvertisementDataLocalNameKey in the BLE advertising data?

OTA name? What would that be for a Bluetooth Peripheral advertising over BLE? I thought the label shown below the image asset came from the name provided in the display items passed in when displaying the accessory picker? Same as the asset itself.