For me neither… could it perhaps just be broken in modern iOS versions? When did you see it last time?

Did you find a method in the meantime? I don't care about app-store-safe or not, but it's pretty annoying that this is no longer possible, in particular, because iOS15 seems to have broken the auto-connect to known Bluetooth devices for everything but audio devices.

Did you solve your problem? I'm having the same since macOS 12 which seems to have even more stricter rules. My SPM-based command-line-utility https://github.com/mickeyl/core-bluetooth-tool no longer works due to these rules.

I can confirm this. The iPhone mini simulators are pretty much unusable as of Xcode 13. Congrats, this marks a new low in the release of Apple developer tools.

Derive a custom application class and override preferredContentSizeCategory.

Note that softlinks do not impose any problems. I have my DerivedData softlinked to a ramdisk volume and everything is pretty snappy that way.

FWIW, the culprit is the missing inherited permissions. When running the tool from iTerm (which is what I'm using as terminal emulator), it inherits the permissions from it. Granting Bluetooth permissions to iTerm fixes my problem. Now: Is it possible that my command line program can detect this lack of (inherited) permission, thus preventing the crash and rather showing an instruction alert instead?

How did you manage to get the CoreBluetooth security confirmation appear for your command-line app? I'm trying to do the same and said alert only appears when I run the app from lldb.

Same problem with my AppleWatch SE cellular. Unbearable!

Still in iOS 14.3 – I find it mildly amusing, but also irritating that Apple leaves such messages in their builds. It demonstrates a general sloppiness and lack of polish.

It's been a long time, but in the meantime, this bug has been fixed. It's working as of at least watchOS7 (maybe earlier).