Bluetooth-dev

Download

bluetooth-dev@lists.apple.com

May 2019

2 participants
2 discussions

advertisements seen while trying to connect
by Rogers George 17 May '19

17 May '19

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hidrate-me.20150623.gappssmtp.com; s=20150623; h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=iRnFbQGGIkdtgAA5OkCXpQlgoVaPkYRBXBknqrQGYmg=; b=AjS3un2JvgXdVB363rYkF6rRwK0/y7jWW7DGOd9NLf8m0gOfh+7mwaog+KRwUMCD4v MFvEt/A9YfHuzKlPw/xmhPvisHX6DKe+AW1ZfwUPGYrwvv6X51O9Vy9fT2dKvabgH/vw GTZV8G0hCGkyOUOS+0p33ypIx7aomvgZxlOdcCM1UaE4KD5d1wcow3BwkdX+ZUORKgaM /fDg4fgYO0T7kQZUpMcyJRWmZ4KVhtxav6SoPeTBA+wRD5uCM0N0y785OpB6us2YITnD 3CE9wplr5BmCuHVkmr26fALK+3Q3i0Fx7ehyI4dHdbEUlA1Ji/TOnerqmP+J6xwyXKYc uiFA== I want to make sure this is normal, expected behavior, and I'm mitigating it properly. Our app connects to a Cypress PSoC-4 based peripheral. Normally, when our device advertises, we see: our CBCentralManager calls our delegate's centralManager(_ central:, didDiscover peripheral:, advertisementData, rssi RSSI:); we call connect(peripheral) if appropriate; and eventually our delegate gets a call to centralManager(_ central:,didConnect peripheral:). All as expected, well and good. But. >From time to time, our peripheral would be powered on, in range, the corresponding CBPeripheral would be in the .connecting state, app in foreground... and no connection would happen. Sometimes after waiting several minutes it would connect, sometimes not. Turning bluetooth off and on (using airplane mode, so bluetooth really did get turned all the way off) always resulted in immediate connection success. Adding the CBCentralManagerScanOptionAllowDuplicatesKey to our scanning confirmed that the delegate was still getting repeated calls to the didDiscover method. Thus, our mitigation: when we see advertisements for a peripheral that we're trying to connect to, if we see more than six in 1 minute with the peripheral still in .connecting state, we cancel and retry the connection attempt. This seems to mostly work. We also log an event to Crashlytics, where we see that this is happening to 20% of our customers! Is this right? Is this how Core Bluetooth is expected to behave? Is there something I could be doing differently, or a better mitigation strategy? We've seen this on all iOS since 9. (I've asked about this before, am trying for less verbosity this time) -- R. _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)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(a)lists.apple.com

1 0

One CBPeripheralManager instance serving multiple CBCentral instances causing disconnected.
by BaThach Nguyen 16 May '19

16 May '19

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=TgOKk60cCvsh/Vx1DaRTTEgsO4D8glBM7P1iT9N+L+k=; b=VFWkSdRP9cs9abuYdx0TaeXYUaSdAPRfuF9ALNcODsrwKkKAc59Aq8tWmv7GP/IHf9 Gd1uq9C/ZvQHuyVKCTrIDKmAvXm68ry7GiNPy3l0I+zBCAZN82d36rssGWJLWT62UT+i 9pk6kQUuM21AKMDerEtaAh3P2FDRqAq7ziXewk7S528HlHUJbP8a21pqxlk/fNmTC7fM XWFNRi4RS7U7o2J/BdghD8XIw+mGv1Vckym5ehYVpaffJT4oses+VVjZliXntEVqDFqe 8OwUbxWR/lE3u7woPoivbtUXvoVeLJIEoKJVc2+vvOpCMWgwLGSyFQ5rDDSk9tMROpJb dFcw== Hi everyone, I have an app, which using CoreBluetooth and play both roles Central and Peripherals. This app get the information from an IoT device, and then forward it to other apps via notifying. - App1 has one CBCentralManager instance to connect to IoT device (peripheral) to get data. - App1 also has another CBPeripheralManager instance, to advertising and notifying the data it got from IoT device (via predefined ServiceUUID so App2 and App3 can scan). - App 2 and App 3 play as Central roles, having CBPeripheralManager to connect to App1, subscribe for notification from predefined characteristic. And getting data whenever App1 notify it. When App2 and App3 connect to App1, it causes the connection from App1 to IoT device resetting quite often. I saw centralManager:didDisconnectPeripheral:error: every 5-10minutes. The reason for IoT device disconnected to App1: default 16:31:51.032169 -0600 MyBLEApp Disconnected peripheral (error: Error Domain=CBErrorDomain Code=6 "The connection has timed out unexpectedly." UserInfo={NSLocalizedDescription=The connection has timed out unexpectedly.}) When App2 and App3 don't connect to App1, the connection between App1 and IoT device is pretty stable. I also posted question here with more logs, but no reply yet: https://forums.developer.apple.com/thread/116525 I thought so many data notifying caused this issue, but when I tried to remove all code sending/receiving data between App1, and App2/App3, just connect App2 and App3 to App1 (just call connectPeripheral:options:, stay connected), issue still happened. Is there any idea how that can be happened? Thank you! -- Best, Andy _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)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(a)lists.apple.com

1 0