I am writing to seek assistance regarding an iBeacon implementation issue we are experiencing in our iOS application. Issue Description: We have successfully implemented iBeacon functionality in our app, but we are encountering a specific problem with background region monitoring: When app is in foreground: Our app successfully detects iBeacon signals and triggers notifications when entering beacon regions. When app is terminated: Our app fails to respond when entering our own iBeacon regions. However, we have observed an interesting behavior: Third-party iBeacon apps can still detect and trigger notifications for their beacon regions After a third-party app triggers, our app suddenly starts receiving notifications for our own iBeacon hardware Technical Details: iOS Version: 18.0 Xcode Version: 16.。4 Device Models Tested: iPhone 15 Pro Questions: What could be causing our app to fail detecting iBeacon regions when terminated, while third-party apps work correctly? Why does our iBeacon detection start working only after another iBeacon app triggers? Are there specific implementation requirements or best practices for reliable background iBeacon monitoring? Could this be related to iOS background app refresh policies or system resource management? Current Implementation: We have implemented the standard Core Location framework with: CLLocationManager with appropriate authorization Region monitoring setup with CLBeaconRegion Background modes enabled for location services Proper delegate methods implemented We would greatly appreciate your guidance on resolving this issue, as it significantly impacts our app's user experience. Thank you for your time and support.

I am debugging ImageCaptureCore to communicate with external cameras. When I called the PTP function below to send a command and add data, the response timed out for more than 5 seconds. After waiting for a period of time, I obtained the response. However, the response callback function obtained responsivData.length as zero and ptpResponseData.length as zero too. (void)requestSendPTPCommand:(NSData *)ptpCommand outData:(NSData *)ptpData completion:(void (^)(NSData *responseData, NSData *ptpResponseData, NSError *error))completion; data is below: Wrote 1 = 0x1 bytes PTP：send data: (hexdump of 1 bytes) [ ] I/PTP (14564): 0000 01 - .

We are develop an application with corebluetooth framework. we connect to device with ble. and open two l2cap channels. it can transfer data with stream. but when it close the second l2cap channel, it always close the first l2cap channel.

My MacBook speakers have started crackling on every sound since macOS 26 Beta 1, the problem is still the same on Beta 9. Happens especially when Simulator is opened.

Hello, We are testing Wallet passes with iBeacons in iOS 26 Beta. In earlier iOS releases, when a device was in proximity to a registered beacon, the corresponding pass would surface automatically. In iOS 26 Beta, this behavior no longer occurs, even if the pass is already present in Wallet. I have not found documentation of this change in the iOS 26 release notes. Could you please confirm whether this is expected in iOS 26, or if it may be a Beta-specific issue? Any pointers to updated documentation would be appreciated. Thank you.

According to Accessory Design Guidelines iPadOS support HID trackpad. Is there a design example of such supported devices? I have tried to adapt device software to guidelines without any result on iPad.

Hello, The Apple Pencil Pro brought with it the UICanvasFeedbackGenerator API, which lets us trigger haptic feedback on discrete events initiated by the pencil. That works fine. My question then: is it possible / are we "allowed" to trigger haptic feedback on events that weren't initiated by the pencil? For example, say the user is using a left hand finger to drag a slider, while holding the pencil in their right hand-- would it be possible to make the pencil vibrate to indicate the dragged slider knob reached a certain point? Or is the rule that vibration is only possible/allowed when the pencil itself generated a touch? Thanks!

I have some logic which requires NFC support on the device. This is what I'm using to make sure that it's available: isNFCMissing = !NFCNDEFReaderSession.readingAvailable && !NFCTagReaderSession.readingAvailable && !NFCVASReaderSession.readingAvailable Is it possible for isNFCMissing to be true even if the device has an NFC chip. The minimum iOS version for the application is 16 which is only supported on devices with an NFC chip to begin with.