When attempting to build an Apple Vision Pro application written in Swift in Xcode, we get the following status errors: "Provisioning profile [Profile Name] doesn't include the Main Camera Access capability.” and "Provisioning profile [Profile Name] doesn't include the com.apple.developer.arkit.main-camera-access.allow entitlement.” The provisioning profile we are attempting to use DOES have the Main Camera Access capability enabled through the Apple Developer portal. We have tried deleting and remaking the profile multiple times, as well as creating new profiles with the same settings, but completely different names and bundle identifiers, but keep getting the same errors. We DO have the "com.apple.developer.arkit.main-camera-access.allow” added to the entitlements file of the Xcode project, and we DO have the “NSMainCameraUsageDescription” key added to the info.plist file, along with the needed string describing the camera usage.
Our organization has a valid and active Enterprise account, through which we have requested and been granted access to the “Main Camera Access” capability. We have built this applications multiple times before in the past year with no issues, these errors began after one of our provisioning profiles expired and we re-made it. We have tried clearing the Provisioning Profile Cache on our machine, clearing the Derived Data in the Xcode settings, and clearing the Xcode build cache. We are experiencing these errors on multiple machines, with different versions of our app, and with completely different apps that use the Main Camera Access entitlement. We experience these errors when the profile is downloaded directly in Xcode, and when it is downloaded from a browser and imported into Xcode. When we use “Automatically manage signing” our app properly builds and deploys to the Vision Pro, but when we use the app and attempt to access the main camera, the app crashes with the exception: "Exception: This app failed to request an authorization.” We have searched online forums and found several instances of others that have experienced this problem, but have not found a solution that works.
Software Versions:
Xcode Version: 26.6
macOS Version: Tahoe 26.5.1
VisionOS Version: 26.5
I suspect that you were only granted this capability for development. You can check that for yourself using the process described in Finding a Capability’s Distribution Restrictions.
When we use “Automatically manage signing” our app properly builds and deploys to the Vision Pro
Right. That’s because automatic code signing uses development signing identities and profiles, and the capability is available to you in that case.
but when we use the app and attempt to access the main camera, the app crashes with the exception
That’s probably a different issue. If you still had provisioning problems, you app wouldn’t build or run. The fact that it builds and runs indicates that your entitlements are all good.
But let’s run a test, just to confirm that:
- In Xcode, build and run your app on the device.
- Still in Xcode, choose Product > Show Build Folder in Finder.
- Navigate to Products > Debug-xros.
- Dump the entitlements:
% codesign -d --entitlements - /path/to/your.app
…
[Dict]
[Key] application-identifier
[Value]
[String] SKMME9E2Y8.com.example.apple-samplecode.Test844352
[Key] com.apple.developer.team-identifier
[Value]
[String] SKMME9E2Y8
[Key] get-task-allow
[Value]
[Bool] true
I expect you’ll see com.apple.developer.arkit.main-camera-access.allow listed there.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"