Search results for

We are unable to process your request

69,611 results found

Post

Replies

Boosts

Views

Activity

Unable to use Bluetooth in watchOS companion app if iOS uses AccessorySetupKit
FB18383742 Setup 🛠️ Xcode 16.4 (16F6) 📱 iPhone 13 mini (iOS 18.0.1) ⌚️ Apple Watch Series 10 (watchOS 11.3.1) Observations As AccessorySetupKit does not request Core Bluetooth permissions, when a watchOS companion app is installed after having installed the iOS app, the toggle in the watch settings for Privacy & Security > Bluetooth is turned off and disabled After removing the iPhone associated with the Apple Watch, Bluetooth works as expected in the watchOS app Upon reinstalling the iOS app, there's a toggle for Bluetooth in the iOS ASK app's settings and the ASK picker cannot be presented 🤨 From ASK Documentation: AccessorySetupKit is available for iOS and iPadOS. The accessory’s Bluetooth permission doesn’t sync to a companion watchOS app. But this doesn't address not being able to use Core Bluetooth in a watch companion app at all 🥲 Reproducing the bug Install the iOS + watchOS apps Launch iOS app, tap start scan, observe devices can be discovered (project is set up to find heart rate
3
0
791
1w
Reply to Xcode Signing Fails: Provisioning Profile "doesn't match" com.apple.developer.driverkit.userclient-access entitlement
Hi Kevin, Thank you for the detailed response. Here is a summary of our tests based on the solutions you proposed: Regarding the userclient-access Entitlement: We discovered a human error in our initial entitlement request (we had entered the wrong Bundle ID). We have submitted a new, corrected request with the proper DEXT Bundle ID and are currently awaiting its approval. Regarding the Temporary Solutions: To continue development while waiting, we tried your other suggestions, but are still blocked. App Sandbox: We confirm that com.apple.security.app-sandbox is set to false in our app's entitlements. This alone did not solve the issue. IOKit User Client Class Temporary Exception: We implemented your third suggestion precisely. Our app's .entitlements file for this test was configured exactly as follows: com.apple.security.temporary-exception.iokit-user-client-class IOUserUserClient com.apple.security.app-sandbox com.apple.developer.system-extension.install com.apple.security.get-task
Topic: App & System Services SubTopic: Drivers Tags:
1w
My Vision for AI and Algorithmically Optimised Operating Systems
Bear with me, please. Please make sure a highly skilled technical person reads and understands this. I want to describe my vision for (AI/Algorithmically) Optimised Operating Systems. To explain it properly, I will describe the process to build it (pseudo). Required Knowledge (no particular order): Processor Logic Circuits, LLM models, LLM tool usage, Python OO coding, Procedural vs OO, NLP fuzzy matching, benchmarking, canvas/artefacts/dynamic HTML interfaces, concepts of how AI models are vastly compressed and miniaturised forms of full data, Algorithmic vs AI. First, take all OO Python code (example) on GitHub (example), then separate each function from each object into its own procedure (procedural logic) by making a logical procedural list of actions to perform only that function based on its entire dependency chain (i.e. all other objects it relies on). Relate all compiled functions using (for example) fuzzy matching on the name, or AI-based functional profil
3
0
260
1w
Problems recording audio on Tahoe 26.0 (Intel only)
I have some tried-and-tested code that records and plays back audio via AUHAL which breaks on Tahoe on Intel. The same code works fine on Sequioa and also works on Tahoe on Apple Silicon. To start with something simple, the following code to request access to the Microphone doesn't work as it should: bool RequestMicrophoneAccess () { __block AVAuthorizationStatus status = [AVCaptureDevice authorizationStatusForMediaType: AVMediaTypeAudio]; if (status == AVAuthorizationStatusAuthorized) return true; __block bool done = false; [AVCaptureDevice requestAccessForMediaType: AVMediaTypeAudio completionHandler: ^ (BOOL granted) { status = (granted) ? AVAuthorizationStatusAuthorized : AVAuthorizationStatusDenied; done = true; }]; while (!done) CFRunLoopRunInMode (kCFRunLoopDefaultMode, 2.0, true); return status == AVAuthorizationStatusAuthorized; } On Tahoe on Intel, the code runs to completion but granted is always returned as NO. Tellingly, the popup to ask the user to grant microphone access is never displ
2
0
395
1w
Reply to SwiftUI's tabViewBottomAccessory API Cannot Control Visibility in iOS 26.1
There's no supported way for you to programmatically hide the bottom accessory in a tab view with the APIs currently available. If you'd like us to consider adding the necessary functionality, please file an enhancement request using Feedback Assistant. Once you file the request, please post the FB number here. If you're not familiar with how to file enhancement requests, take a look at Bug Reporting: How and Why?
Topic: UI Frameworks SubTopic: SwiftUI
1w
Reply to 'tabViewBottomAccessory' leaves an empty accessory area when conditionally hidden
This is the intended behavior, at the moment there is no API that enables you programmatically hide the bottom accessory in a tab view. The tabview bottom accessory is still configured in this case, but it’s an empty view. If you’d like the engineering team to add functionality that enables programmatically hiding the bottom accessory in the tab view, please submit an enhancement request via Feedback Assistant and post the Feedback ID number here.
Topic: UI Frameworks SubTopic: SwiftUI
1w
Reply to Xcode Signing Fails: Provisioning Profile "doesn't match" com.apple.developer.driverkit.userclient-access entitlement
Following up with this to clear up some odds and ends: Provisioning profile ... doesn't match the entitlements file's value for the ... userclient-access entitlement. One thing to be aware of her is that Xcode has a bias in the way it presents codesign errors where it assumes the Entitlement.plist is correct and the profile is wrong. However, in practice that's basically never the case with DriverKit entitlements and tends to lead to a lot of flailing trying to somehow fix the provisioning profile. This error ALWAYS means that the entitlement.plist doesn't match the profile. You fix that by: Changing the Entitlement.plist to match the profile. Changing the actual profile. That means either: Submitting a new request to correct any mistake (this case). IF you have been granted multiple instances of the same entitlement, then you switch to manual profile generation and manual codesigning. See this forum post for more details on that flow. However, the key here is to understand that this: ...our hypothes
Topic: App & System Services SubTopic: Drivers Tags:
1w
Reply to 'tabViewBottomAccessory' leaves an empty container when conditionally hidden
Thank you for your post. I am unable to locate your FB number for verification purposes. Have you submitted a bug report regarding this issue? The description is pretty good, however I would also recommend a focused sample showing the issue for engineering. If so, please share a link to your test project. That'll help us better understand what's going on. If you're not familiar with preparing a test project, take a look at Creating a test project. Then I would recommend to open a bug report. Once you open the bug report, please post the FB number here for my reference. If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Albert Pascual
  Worldwide Developer Relations.
Topic: Design SubTopic: General
1w
Failed to notarize a "distribution" pkg
I believe that this is related to the post https://developer.apple.com/forums/thread/790880. I essentially have the same problem that they did. I submit my Distribution PKG for notarization but the notarization fails and when I attempt to install the PKG user the UI I get a External component packages (3) trustLevel=0 (trust evaluation failed; treating as invalid due to higher trust level for parent product archive) However if I install using sudo installer -verboseR -pkg ConcealDistribution.pkg -target / everything works as expected. The difference between me and the other post is that when I expand my PKG using pkgutil --expand I do not have a Resources folder within my top level distribution. Instead my structure looks like ConcealDistribution ├── Distribution ├── ConcealConnect.pkg ├── ConcealBrowse.pkg └── ConcealUpdate.pkg The specific notary service errors I receive are as follows { logFormatVersion: 1, jobId: 7e30e3fd-1739-497c-a02e-64fbe357221d, status: Invalid, statusSummary: Archive contains critic
1
0
154
1w
watchOS 26.0.2+ Health Data Sync Failure - Series 7 - FB20533870
I'm reporting a critical Health data synchronization failure that began immediately after updating from watchOS 18 to watchOS 26.0.2 (stable release) and persists in watchOS 26.1 beta 2. Bug Description: Complete failure of Health data sync from Apple Watch to iPhone Health app. All health metrics are being captured and stored locally on the watch but fail to sync to the paired iPhone. Affected Data Types: Activity rings (Move, Exercise, Stand) Heart rate measurements Sleep tracking data Workout data All other HealthKit data points Environment: Device: Apple Watch Series 7 Initial failure: watchOS 26.0.2 (23R362) - stable release Current: watchOS 26.1 beta 2 (23S5052c) Paired iPhone: iPhone 17 Pro Max, iOS 26.1 beta 2 (23B5052c) Bluetooth and Wi-Fi connectivity: Normal Watch pairing status: Connected and functional for all other features Reproduction: Updated Apple Watch Series 7 from watchOS 18 to watchOS 26.0.2 on September 30, 2025 Health data sync ceased completely starting October 1, 2025 Issue persists
1
0
77
1w
Reply to watchOS 26.0.2+ Health Data Sync Failure - Series 7 - FB20533870
Thanks for the post and filing the bug, very good description. I would recommend you to work with the engineering team that are reviewing your bug right now. You can see the status of your feedback in Feedback Assistant. There, you can track if the report is still being investigated, has a potential identifiable fix, or has been resolved in another way. The status appears beside the label Resolution. We're unable to share any updates on specific reports on the forums. For more details on when you'll see updates to your report, please see What to expect after submission. Albert Pascual
  Worldwide Developer Relations.
1w
Reply to Adding App Icon to Xcode for Tahoe
Thank you for the quick response that seems to have moved me forward quite a lot. Sadly it still doesn’t work. My project had an asset catalogue containing the old icon files (called images.xcassets) that I deleted. I created a new one, with the default name and inserted it at the top level of my project. I was then able to import the icon file that I called IconFile. That name is consistent with the name in Project > General; I did not tick “Include all icon assets”. This didn’t work, even after a restart the old icon was still displayed. I then found that the icon file entry in my …-info.plist file still referred to the old icon (that I had removed) so I changed that to AppIcon.icon. That didn’t work either. I cleaned the build folder, the app still runs but has a blank icon (being the outline containing the glass template in white on a pale grey background). Assets.xcassets contains one item being the AppIcon. This is displayed as its three layers plus icon.json that references these and looks credible
1w
Failed to set up credentials.
I received this message when trying to submit a build using Rork.com. Can anyone tell me what this is and how to fix it? There is a problem with the request entity - You are not allowed to create 'iOS' profile with App ID 'XXXXXXXX'. ✖ Failed to create Apple provisioning profile Error: build command failed.
2
0
44
1w
declarativeNetRequest redirect action causing page reload/error in Safari 26.0
After updating to Safari 26.0 (on macOS Sequoia or Tahoe), the Declarative Net Request (DNR) API rule with type: redirect no longer works as expected. When the rule is applied, the browser initially shows a banner at the top of the page: This webpage was reloaded because a problem occurred. After the reload, the page fails to load and displays an error page with the message: A problem repeatedly occurred with https://extensionworkshop.com/?test=true This behavior is new in Safari 26.0. The same rule was working correctly in earlier Safari versions (17.x / 18.x).
1
0
146
1w
Reply to DriverKit. Data Integrity issue.
There are no DispatchSync calls in our code. Here is the SCMD_DONE: Actually, there is, it's just implicit. Correlating your code with the crash log: Thread 8: ... 2 SCSIControllerDriverKit 0x195e8b364 IOUserSCSIParallelInterfaceController::ParallelTaskCompletion(OSAction*, SCSIUserParallelResponse, int (*)(OSMetaClassBase*, IORPC)) + 156 3 com.mycompany.driverkit.MyDevice 0x1042a6a20 invocation function for block in OsBridge::SCMD_DONE(void*, megasas_cmd_fusion*, SCSIUserParallelResponse*, megasas_cmd_fusion*) You're here: ghc->ivars->sentQueue->DispatchAsync(^{ -> ghc->ParallelTaskCompletion(act, lResp); I don't know enough about the exact details of how you've configured your queues to be certain about what's going on, but I suspect what's going on is that ParallelTaskCompletion is implicitly targeting the crashing thread: Thread 5 Crashed:: : 0 libdispatch.dylib 0x19671aa8c __DISPATCH_WAIT_FOR_QUEUE__ + 484 1 libdispatch.dylib 0x19671a5d0 _dispatch_sync_f_slow + 152 2 DriverKit 0x195d3fc1c
1w