Posts

Post not yet marked as solved
2 Replies
2k Views
In the WWDC19 Session 901 "What's new in Core Bluetooth" they mention the new Transport Bridging Key which allows to connect BT profiles like A2DP via the Core Bluetooth API:"We've done so this year by introducing a new concept called bridging.Bridging works by taking advantage of low energy proximity to bring up BR/EDR profiles such as A2DP, HFP, AVRCP.This will work on all devices that support CTKD and to take advantage of it in your application, it's extremely easy.You'll use a new key in the CBManagerConnect, and it's called the TransportBridgingKey.You add it in the option dictionary."There is no documentation on this feature or the new transport bridging key whatsoever.What's the state of this feature? Is this scheduled for a later iOS 13.x release?
Posted Last updated
.
Post not yet marked as solved
0 Replies
901 Views
Somehow the pattern to connect a CBPeripheral has changed with 13.1 compared to 13.If the CBPeripheral reference was retrieved from a BLE scan and connection is created on that CBPeripheral, service discovery and pairing works as expected. Also, classic pairing and address resolution will be done.I then store the UUID of the CBPeripheral and disconnectNext, I try to get the CBPeripheral via CBCentralManager.retrievePeripherals() passing in the UUID and connect to it with connect CBCentralManager.connect() this works as expected on iOS 13 GM (BLE GATT is connected, regardless of whether Classic is connected or not)this fails on iOS 13.1 Beta 2 from the logs it looks as if connection attempt via Classic GATT is made but the CBCentralManager delegate connection callbacks neverin that case, the only way to connect to a previously known CBPeripheral is by using the reference that was retrieved from the centralManager connectionEventDidOccur event and pass that to the CBCentralManager.connect method...Is this expected? It does not feel right this way.
Posted Last updated
.
Post not yet marked as solved
0 Replies
714 Views
WIth iOS 13.1 Beta 2 we found that our app is not connecting GATT via BLE if the peripheral is already BT classic paired. Instead, it seems as if iOS then prefers to connect GATT via BR/EDR which is something the peripheral is not fully supporting so we need to connect GATT via BLE.Can we somehow force to use GATT via BLE?
Posted Last updated
.