Airpods are connected but they won't play anything while Apple watch is connected. As I try to play something phone freezes for few Seconds and continues to play on the Phone after. The Problem appears only when Apple Watch is connected to the Phone.

Bluetooth Connection Issue: Sudden drop connection between the App and the external BLE device PLATFORM AND VERSION iOS 14.7.1 and above (15.0 beta) The iOS App will connect to an external BLE device with the help of the CoreBluetooth framework. DESCRIPTION OF PROBLEM In iOS 14.7.1 and above (iOS 15.0 beta), observe a sudden drop in the connection between the App and the external BLE device during the firmware upgrade process via Over the Air (file size 500 KB, file type ".bin"). The same App is working fine with iOS 14.6 and earlier versions of iOS. It observes that MTU size is also different in iOS 14.4 and iOS 14.7. When disconnection happened CoreBluetooth -> centralManager: didDisconnectPeripheral delegate method called. The total time required to update BLE firmware is 2 minutes, but approx after a 1-minute or 30 seconds connection is dropping between the App and the BLE device. Do I miss anything that causing a sudden drop of BLE connection, specifically in iOS version 14.7 and above? STEPS TO REPRODUCE Connect the iOS App with an external Bluetooth device and start writing/sending the data from the phone to the BLE device continuously in BLE specified UUID. After some time approx 30 seconds or 1-minute observe a sudden drop in the connection between the App and the BLE device.

We have few external devices which have reached end of life(no more production is available)and we are not getting PPID for the same and without PPID app will be rejected by the App Store during app submission. So can you suggest how we can go ahead and support existing users who are using this device.

We have few external devices which have reached end of life(no more production is available)and we are not getting PPID for the same and without PPID app will be rejected by the App Store during app submission. So to discontinue support for this external devices, just removing the corresponding protocols from Supported external accessory protocols in plist is suffices or entire code related to this external device support should be removed from the code base to avoid rejection in the Appstore submission. Kindly suggest.

There is Apple certified adapter for USB C to multiport (HDMI & USB 3.0) which can be used to connect new iPad and Macbooks to monitor and keyboard/mouse - https://www.apple.com/shop/product/MUF82AM/A/usb-c-digital-av-multiport-adapter But for iPhones, there are only single port adapters like the following: Lightning to HDMI - https://www.apple.com/shop/product/MD826AM/A/lightning-digital-av-adapter Lightning to USB 3.0 - https://www.apple.com/shop/product/MK0W2AM/A/lightning-to-usb-3-camera-adapter Is there any Apple certified multiport adapter for iPhone that can be used to connect monitor, keyboard and mouse? I can see some 3rd party adapters like the following: https://www.amazon.com/Adapter-Charging-Splitter-Keyboard-Ethernet/dp/B087MZYRY6/ https://www.amazon.com/Lightning-Adapter-Converter-Delivery-Compatible/dp/B08T913J3D The reviews are mixed for these and not comfortable using them as they are not certified. Any idea why there are no certified/Apple approved options available?

Assalam Alikum / Hi , Hope so everyone is fine and doing good. Am facing an issue retrieving the Bluetooth devices list surrounding me. I have Bluetooth Door which will be open through my iOS application. But I can't find that name in my list. Even I found some Bluetooth devices without names. Thanks in advance.

When my Mac application is connected with external usb device foot pedal controller. For only macOS Monterey usb device foot pedal will send unexpected right click command before specified click command. When I run my application in macOS Monterey my application always got unexpected right click command first and then click command if I press click command from usb device foot pedal. Is there any system setting I need to change for macOS Monterey to use external usb device foot pedal ?

Need to communicate with classic Bluetooth device(Bluetooth v2.0 + EDR). We have a medical device which has classic Bluetooth. We need to communicate with that medical device using iPad using Classic Bluetooth communication. We are not able to scan and connect to the nearby classic Bluetooth devices from our application. So can you please let us know whether classic Bluetooth communication can be done in iOS or not.

Issue Details: When EAAccessoryManager object is created using below line:- let eaManaer = EAAccessoryManager.shared() Sometimes, It takes too much time to initialize the object nearly about 5-10 seconds it takes to initailize the object. When this happens, if you take your app to background and bring the app to foreground the application gets hanged and crashed. Recovery: Restart the iPhone. After restarting the iPhone, EAAccessoryManager object starts initializing normally within milliseconds and application does not hang when goes to background and comes to foreground. Also, one observation: If app does not initialize the object of EAAccessoryManager then we are not able to see this issue.

Normal status, IPhone connects the external equipment through the USB interface, the iphone battery icon flashes the state of charge and then restores the original state, Then App received EAAccessoryDidConnectNotification callback,Then start data interaction. But in iOS 14 and later system(Test is 14.6 and 14.7)Sometimes the charging state does not disappear, EAAccessoryDidConnectNotification Callback is not received, Data interaction also cannot be performed.

External usb foot pedal driver should not generate mouse click NSEvents In Monterey external usb foot pedal driver unexpectedly also acts as a mouse device and generates NSLeftMouseDown/NSRightMouseDown events. If I click the middle button of external usb foot pedal and then NSRightMouseDown gets received then it has to be a system problem (or a driver problem) How to solve this issue?

When I was developing Find My Network Accessory, I only modified the Product data in Find My Network Accessory ADK (Nodric DK nRRF52), Unable to identify products in iPhone 12's Find My App. The original ADK will identify as bike. Is there a situation where Find My App only identifies three products on the official website? How do I make Find My App recognize the modified Product Data?

Hi, I recently switched from Android to iPhone 12 Pro. My car is Skoda Octavia 2015. Since the very first time my iPhone was connected to the car audio, the sound is stuttering once in 15 - 20 seconds, turning my music experience from pleasant to annoying. How come that I have now almost the best phone in the world, and I have problems in a very basic functionality, where, by the way, Android never let me down. Please help! Thank you.

When I connect my son’s Cowin E8 headphones to his iPad 8th generation which is operating on the latest version as of today’s date 9/18/2021 and my son is watching YouTube Kids and he changes what he is watching to a new video he picked, the headphones will disconnect from the IPad. You can always connect them to the iPad but as soon as you change and start watching something different they disconnect. I know this started happening when a new version of IOS was downloaded on the IPad a few months ago. I am 100% sure it is not the headphones because I have tried 3 different ones that are different brands and they all do the same thing. Can anyone help me correct whatever bug this is that is causing this issue. Thank you very much ahead of time!

I have created a small program that needs to connect to an external accessory. I have been able to do so successfully with UIKit and the EA framework. The problem I am having is that I have a SwiftUI based app that needs to use the External Accessory but when I call the showBluetoothAccessoryPicker function, the picker window does not show. What I have tried so far: I have read that you need to have the app delegate with var window: UIWin setup correctly to see the picker window. So I created a class class AppDelegate: UIApplicationDelegate { var window: UIWindow? } I then associated the app delegate with my swiftui "App" struct like this: @main struct POC: App { @UIApplicationDelegateAdaptor(AppDelegate.self) var appDelegate var body: some Scene { WindowGroup { TabSelectionView() } } } Nevertheless, when I call showBluetoothAccessoryPicker the picker window does not show. I see the following in the output log: 2021-09-20 13:16:31.804796-0500 POC[2150:1514447] IAPDHasLaunched: kIAPAvailableNotification iapdAvailableState 0 -> 0 2021-09-20 13:16:31.805791-0500 POC[2150:1514447] IAP2DHasLaunched: kIAP2AvailableNotification iap2dAvailableState 0 -> 0 2021-09-20 13:16:31.807219-0500 POC[2150:1514447] -[EAAccessoryManager _initFromSingletonCreationMethod] isRunningOnMac This log appears correct and matches the output from a working demo app that uses UIKit. It's just that the picker window does not show. Does anybody know what needs to be done to get the picker window to appear correctly for SwiftUI apps? Is there any SwiftUI examples of connecting to an External Accessory that anybody could point me towards? Thanks in advance for any help.

We were DFU-Library to upload firmware to our BLE accessory earlier. But our new set of accessories doesn't support DFU library and we need to upload the firmware to an OTA service in its respective characteristics and we does the same using following code, var offset = 0 var bytesToSend = fromData.count let packetSize = BoardInformationService.packetSize var chunkArray: [Data] = [] repeat { let chunkLength = min(bytesToSend, packetSize) let chunk = fromData.subdata(in: Int(offset) ..< Int(offset + chunkLength)) chunkArray.append(chunk) offset += chunkLength bytesToSend -= chunkLength } while bytesToSend > 0 print("BT: Total Chunk size:\(chunkArray.count)") return chunkArray } func uploadNextChunk() { if let firmwareCharacteristic = fileCharacteristic { print("Found fileCharacteristic to upload") if self.currentPacket < self.totalNumberOfPackets { // Send next chunk let nextPacket = self.fileByteChunkArray[self.currentPacket] print("BT: current packet uploading: \(self.currentPacket)/\(self.totalNumberOfPackets) Data:\(nextPacket)") self.currentPacket += 1 // Write to peripheral BTDiscovery.sharedInstance().peripheralBLE.writeValue(nextPacket, for: firmwareCharacteristic, type: .withResponse) } else { updateCompleteCompletion!() } } else { print("No fileCharacteristic to upload") } } // This is a delegate method which gets called when we get response from our peripheral after sending each packet. func ackReceivedFromPeripheral() { uploadNextChunk() } But this doesn't work on iOS but the same approach working on Android. Can you please guide me what could be wrong here.

Hello. I need to connect manufactured accessory that supports WAC provisioning to user's network. How it could be done? What frameworks, certificates, entitlements or algorithms should I use to make it work? Is there any documentation how it works? Thanks in advance.

I can see my pi listed in iOS settings, and I can connect to it that way. I'm also trying to connect using CoreBluetooth but the pi never appears as a Peripheral I can connect to. Should I be taking another approach? Would it appear as an ExternalAccessory instead? I have a Python server on the device that I'd like to connect to. Thanks!

Hi Guys, We have implemented EASession from the firmware side and it's working perfectly. Now we are trying to create EASession with Multiple protocols and we are getting ERROR with identification. Please help us to create EASession with multiple protocols. Thanks in advance.

I had iPhone 6 iOS 12.xx - it worked seamlessly with Vauxhall vector 06 car stereo bluetooth. Upgraded to iPhone 13 iOS 15. It will connect a call to the car bluetooth, but now won't hang up. The phone hangs up, but the car stereo/bluetooth line stays as open as if the line is connected still. Only fix so far to pull stereo fuse from the car each time! Apparently becoming a known issue with Apple at the moment