MacOS 12.0.1 Monterey Bluetooth issues

I'm not sure yet if it's related or not -- but on our side we are normally connecting to RFCOMM over Bluetooth (SPP protocol) for our device. We have failed to open socket connection since the upgrade to macOS Monterey.

After investigation, we found out that:

1. The SDP protocol we had in place did not work exactly the same -- we did not receive an event when SDP completed, which caused our app to fail to try a connection (first issue)

2. We used to look at recentDevices() to connect, and the function failed to return recent devices. pairedDevices() has been working properly.

3. Finally, we have found that under a specific set of circumstances, we are able to connect to RFCOMM. However, this only happens when we "beat" the OS to the punch, and manage to open the socket before it gets "locked". I cannot confirm this for certain, but it's likely that something is blocking the connection to RFCOMM socket on the OS side. An example might be if the OS steals the BLE connection to fetch battery level, preventing us to access the classic bluetooth service SPP. In the cases where we managed to connect RFCOMM, the battery % was not displayed next to the device after connection in the Bluetooth menu. It may simply be a coincidence, but in the past we have observed similar issues when trying to connect within our application both BLE Battery service and classic BT SPP at the same time. One ended up blocking the other...

If anyone's device uses both SPP/Battery level, this may be the issue you are facing. In order to successfully connect on our side, we normally turn off the device, then try to initiate a connection in the OS (which will try for a while but fail since the device is off). However, while it's trying, and before it fails -- if you turn on the device and enable RFCOMM, there is a chance you can successfully establish the socket connection. Once the connection is established on our side, it's stable.

Apple has six hours of my life that I'll never get back trying to resolve this. Four hours on the phone and two hours in the store. The store representative ACTUALLY said, 'iPhone and Mac normally do not connect using bluetooth'. Well, I've been connecting (and using and needing) this bluetooth connection for years. Five Apple representatives and they don't have a clue. To their defense, they reset everything they could. BTW, if you think you can just go back to Big Sur to get your Bluetooth back, it isn't so easy. Good luck everyone!

Yep - same issue with Bluetooth hanging. Keep a wired mouse around now to reset the Mac. Ore plug lightening cable into keyboard and do it that way. Seems random. iMac 2017. Monterey. LoadsaRam etc.

Bluetooth has always been poor on Mac - had problems with headphones etc.

Looks like BT exploded..

Mac-Mini 2018 MacOS 12.0.1 (21A559) VictronConnect App crashes upon reaching 20% of the connecting process. Then a notification pops up with the error "Problem Report for VictronConnect"

This started after updating MacOS 12.0.1, as of today 12-8-2021

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 Terminating Process: exc handler [2134]

Still works on my iPhone 8 Plus IOS 15.1

Hi there!

I've been through this for weeks, using Monterey without any success bluetooth connection. Until today, its work perfectly smooth.

I simply using application called ToothFairy for bluetooth connection and my magic mouse is all functioning again. No more connect-disconnected randomly.

Gonna try this for more days.

Hope its help.

Thank you.

My Apple Wireless Keyboard is no more able to connect with bluetooth after update to Monterey. Need fix!

My Qt BLE apps ran fine in earlier macos, but did not run on my 2021 Powerbook M1 Max (Monterey macOS 12.0.1, Xcode 13.1). I noticed that Lightblue and nRFConnect BLE tools ran fine on the M1, so I suspected that this was a permissions issue with Qt-created apps. I used Xcode to edit the plist template in clang_64/mkspecs/macx-clang/Info.plist.app to add 5 permissions

<key>Privacy - Bluetooth Always Usage Description</key>\n
<string>App uses BLE</string>\n
<key>Privacy - Bluetooth Peripheral Usage Description</key>\n
<string>App uses BLE</string>
<key>Privacy - Location Usage Description</key>
<string>App uses BLE</string>
<key>Privacy - Location Always Usage Description</key>
<string>App uses BLE</string>
<key>Privacy - Location When In Use Usage Description</key>
<string>App uses BLE</string>

Delete your shadow-build directory, use Qt Creator to re-build (which uses the new plist with BLE permissions), and now Qt BLE apps run on Monterey!

Same here. Sometimes when I try to connect something like a controller, it asks me to put in a code. I'm sure it has to do with something in the bluetooth drivers.

I have weird issues with an open-source library that uses Bluetooth which I have not seen before. I am guessing it is the same issue.

Does anyone know whether it should have been fixed in 12.1?

Same here - since installing Monterey on my mid-2015 15 inch MBP my Bluetooth keyboard loses its pairing after a few hours of (keyboard) standby. I have to delete it from Bluetooth devices and re-pair it. Previously I could just hit one of the keys, and, after a couple of seconds, the Mac would recognise it.

Same here.

Device: iPhone iOS 15.0 & iMac macOS monterey 12.2

Question: After I update macOS system newest version,The Bluetooth connection does not match. Even if it is connected, it will be disconnected immediately.

The issue can be still reproduced on Monterey 12.2. Apple has not respond to my bug report.

Apples Motto: Move fast and break things, they got the money, you the bill.

The same problem is occurring here...

iOS 15.2.1 Monterey 12.2

The error message tells that the device is not compatible.

Found an interesting half-solution for apps that use Bluetooth: Reset the Security & Privacy settings for this app in Bluetooth section.

Background:

1. Custom QT app for custom BLE device.
2. The app crashes when connecting to the device.
3. After Monterrey 12.1 update the app started working, but for the first run only.
4. Reinstalling the app didn't help.
5. It was accidentally found that when a prompt about "APP would like to use Bluetooth" is shown and agreed - the app is able to safely and soundly connect to the Bluetooth device. Once the app is closed these settings must be reset manually for the next run.

Very disappointed that there is no fix for the Bluetooth issue yet. It has been a few months since the first report and the update 12.2 didn't change a thing. Airdrop and wireless mouse not working, weirdly the wireless keyboard is functioning???? Have noticed that my com.apple.Bluetooth.plist is gone from the library??? I would suggest all those clever minds put in some overtime.