This issue happens on iOS 6 and iOS7. Usually when services of peripheral are discovered, the method: - (void)discoverCharacteristics:(NSArray *)characteristicUUIDs forService:(CBService *)service will get called. Then we call the - (void)peripheral:(CBPeripheral *)peripheral didDiscoverServices:(NSError *)error method to discover the characteristics. But in my app, the peripheral.services is sometimes empty(This happens occasionally, but it's bothering since the characteristics cannot be found). The worse part is that when the peripheral is in this state, it's services keeps empty until I kill the peripheral app(an iOS app too) and restart the app again.
From the aspect of usability, we shouldn't tell the user that "You should kill the app and restart it and try again" right?
Has anyone seen this issue when you develop a central app? And I'm not sure if it's a iOS issue or my app's issue. Any engineer from Apple can answer my question? I'll be really appreciated. _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.... This email sent to site_archiver@lists.apple.com