Previously working! Now Broken. I developed a test application to establish a connection with a BLE peripheral. The application successfully connected to the peripheral, but it did not establish SMP Pairing procedure. Previously, I was able to successfully pair with the devices during the Beta phase. However, currently, I am not receiving the OS prompt to grant Bluetooth permissions. I understand that this may be a newly introduced feature in the recent releases. Could you please provide guidance on whether there is a specific flag that needs to be enabled or added elsewhere, or if this is a bug with the ASK? PLEASE HELP!!!

I'm using AccessorySetupKit to use multiple devices in my app. The problem I'm facing right now is that each time I want to add a new device with an ASAccessorySession, the CBCentralManager state (which was previously .poweredOn, as I has already connected a device) rapidly changes states from .poweredOn to .poweredOff, and back to .poweredOn again. The consequence of these state changes is that any connected device is instantly disconnected, and I need to reconnect them one by one. Is that the normal behavior?

I want to observe/capture logging from my iPhone app when its not running via Xcode. However when using either the Mac's console app, or the console functionality within Apple Configurator, after about 2 or 3 seconds the logging disappears off the console. How can it be prevented from doing so?

Development environment: Electron 30.2.0 Run-time configuration: macOS 14.5 (23F79) DESCRIPTION OF PROBLEM I have one keyboard which will wake up the Mac OS from sleep when sending command to it at the time system starting to sleep. But this keyboard will not have such problem on Window OS, I don't know why sending command to that keyboard will wake up the Mac OS system from sleep. Does anyone know from a hardware or software point of view, what kind of usb keyboard operation will cause the macos system to wake up? Or can someone give us guidance, how to debug and solve the usb keyboard caused by the wake up system problem on Mac OS system? STEPS TO REPRODUCE Sending command to that keyboard when the system start to sleep

I recently got an iPhone 16 Pro Max, and I’m currently running iOS 18.1 Beta 5 (22B5054e). I’ve noticed an issue when charging overnight with MagSafe. My phone stops charging, and last night it stopped at 63%. I’m also having problems when charging via cable. It shows “slow charger” even though I’m using a 100W charger. Is this an issue with iOS 18.1 or could it be a defect with the iPhone itself? I didn’t experience this with my iPhone 15 Pro Max. Thanks

Since updating my iphone 12 to iOS 18, my phone either doesn’t charge unless the wire is in a certain position or if it is charging it’s very slow. I’ve tried multiple wires with multiple plugs and it’s all the same. I had no issues before updating and now wish I hadn’t updated because I can’t afford to go and buy a new phone.

Development environment: Electron 30.2.0 Run-time configuration: macOS 14.5 (23F79) DESCRIPTION OF PROBLEM I have one keyboard which will wake up the Mac OS from sleep when sending command to it at the time system starting to sleep. But this keyboard will not have such problem on Window OS, I don't know why sending command to that keyboard will wake up the Mac OS system from sleep. Does anyone know from a hardware or software point of view, what kind of usb keyboard operation will cause the macos system to wake up? Or can someone give us guidance, how to debug and solve the usb keyboard caused by the wake up system problem on Mac OS system? STEPS TO REPRODUCE Sending command to that keyboard when the system start to sleep

Hi, we are trying out AccessorySetupKit on our app for pairing with an IoT device via Bluetooth. I can see from this WWDC2024 talk Meet AccessorySetupKit that ASK supports BLE pairing methods with a PIN code. Is that enabled through this bluetoothPairingLE option on ASAccessory.SupportOptions? Is it correctly understood that this is referring to the Secure Simple Pairing feature in the BLE specs? This might be due to my unfamiliarity with Secure Simple Pairing, but does it require the PIN code again after it has been paired but disconnected and then re-connected? Any help here would be greatly appreciated.