Search results for

file uri scheme

79,839 results found

Post

Replies

Boosts

Views

Activity

Reply to Permission error occurs when I use setDefaultApplication(at:toOpen:completion:)
Is your app sandboxed? If so, this is not expected to work. The App Sandbox prevents apps from changing application bindings. You can see evidence for this if you dig into the error. The underlying error, -54, aka permErr, is being rendered as permissions error (on file open) but that’s just an accident of history. Launch Services is using it in the more generic sense of permission denied. And, yeah, please do file a bug against the docs. We should update both the NSWorkspace API documentation and the Review functionality that is incompatible with App Sandbox section of Protecting user data with App Sandbox. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: General Tags:
2w
Reply to "Signing certificate" and post-installation assignment fail due to IOPCIPrimaryMatch
My current goal is to ship the PCIe DriverKit. I want my customers to be able to install our DriverKit without having to disable SIP or anything like that. I tried the following value as suggested, and the build did indeed pass. 0xFFFFFFFF&0x00000000 After checking the contents of the downloaded provisioning file again, I was able to clarify the problem. The value in the file created in App Development wasn't set properly. Created a provisioning file with DriverKit App Development and checked the value of IOPCIPrimaryMatch. 0xFFFFFFFF&0x00000000 Created a provisioning file with the Distribution Developer ID and checked the value of IOPCIPrimaryMatch. 0x00001916&0x0000FFFF Why is there a difference between the Apple Development value and the Developer ID value? My account belongs to a corporate account. Is this related? Also, when I check your post, it seems like I've never created a provisioning file. That's strange. Is the local file on my PC
Topic: Code Signing SubTopic: Entitlements Tags:
2w
xcodebuild failed without clear reason
Hello, I got a weird issue with xcodebuild, the tool gives the error that requested device could not be found but I already add it. The issue is solved if I remove the -scheme (and deveriedDataPath. Do you have any idea what is wrong with the parameter or it is the xcodebuild error itself? haiphan@MacMini MetalTest % xcodebuild -project MetalTest.xcodeproj -destination 'platform=macOS,name=Any Mac' -scheme MetalTest Command line invocation: /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -project MetalTest.xcodeproj -destination platform=macOS,name=Any Mac -scheme MetalTest 2025-12-05 12:18:25.594 xcodebuild[17581:2982049] Writing error result bundle to /var/folders/x7/rmx20t393rx49t6gyx3fh_vdmz2lm8/T/ResultBundle_2025-05-12_12-18-0025.xcresult xcodebuild: error: Unable to find a device matching the provided destination specifier: { platform:macOS, name:Any Mac } The requested device could not be found because no available devices matched the request. Available destina
0
0
30
2w
Reply to DEXT (IOUserSCSIParallelInterfaceController): Direct I/O Succeeds, but Buffered I/O Fails with Data Corruption on Large File Copies
Hi Kevin, Just a quick update: I have uploaded the source code (SetupHBAConstraints_Workaround.cpp) to the bug report (FB21256805). This file confirms that we are indeed defining all the required keys (including kIOMaximumSegmentByteCount) before calling UserReportHBAConstraints, and it also demonstrates the SetProperties workaround we implemented to bypass the issue. Best regards, Charles
Topic: App & System Services SubTopic: Drivers Tags:
2w
pairedUUIDsDidChangeNotification never fires, even with MFi hearing aids paired
Hi everyone — I’m implementing the new Hearing Device Support API described here: https://developer.apple.com/documentation/accessibility/hearing-device-support I have MFi hearing aids paired and visible under Settings → Accessibility → Hearing Devices, and I’ve added the com.apple.developer.hearing.aid.app entitlement (and also tested with Wireless Accessory Configuration: https://developer.apple.com/documentation/bundleresources/entitlements/com.apple.external-accessory.wireless-configuration ). com.apple.developer.hearing.aid.app xxxxx but the app won't even compile with this entitlement Problem NotificationCenter.default.addObserver(...) for pairedUUIDsDidChangeNotification never fires — not on app launch, not after pairing/unpairing, and not after reconnecting the hearing aids. Because the notification never triggers, calls like: HearingDeviceSession.shared.pairedDevices always return an empty list. What I expected According to the docs, the notification should be posted whenever paired device UUIDs chan
1
0
494
2w
Reply to DEXT (IOUserSCSIParallelInterfaceController): Direct I/O Succeeds, but Buffered I/O Fails with Data Corruption on Large File Copies
Yes. We confirmed that kIOMaximumSegmentByteCountWriteKey was correctly set to 65536 (64 KB), and kIOMaximumSegmentCountWriteKey was set to 129. Did you? Because I didn't find IOMaximumSegmentCountWrite or IOMaximumSegmentCountWrite in either of the files you uploaded. More to the point, the class reference for UserReportHBAConstraints lists these seven keys as required: kIOMaximumSegmentCountReadKey kIOMaximumSegmentCountWriteKey kIOMaximumSegmentByteCountReadKey kIOMaximumSegmentByteCountWriteKey kIOMinimumSegmentAlignmentByteCountKey kIOMaximumSegmentAddressableBitCountKey kIOMinimumHBADataAlignmentMaskKey Your DEXT should be defining all of them and, as far as I can tell, it isn't. __ Kevin Elliott DTS Engineer, CoreOS/Hardware
Topic: App & System Services SubTopic: Drivers Tags:
2w
Reply to Permission error occurs when I use setDefaultApplication(at:toOpen:completion:)
Sounds like either it's not working right or the documentation needs to be updated to explain how to get it working. Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. Bug Reporting: How and Why? has tips on creating your bug report.
Topic: App & System Services SubTopic: General Tags:
2w
Reply to Xcode not updating recent projects
Thank you for sharing your experience. It appears that you are encountering an unusual issue with Xcode not displaying recent projects. To resolve this, please ensure that both macOS and Xcode are updated to the latest versions compatible with your system. While you have mentioned your current versions, it is advisable to double-check for any minor updates. Could you kindly provide a screenshot of Xcode when you attempt to open the “Recents” folder using the “File” menu? Please note that the screenshot should display the contents of the “Recents” folder. File -> Open Recent Please indicate whether you observe any recent projects or if the list is completely empty. Albert Pascual
  Worldwide Developer Relations.
2w
Reply to Having trouble with USD material not showing correct color
@ericD_TRI Fantastic, a USDA file is very helpful! I think I understand what is going on, and there is indeed a divergence in how Reality Composer Pro is rendering content vs. how Finder renders. See Validating feature support for USD files for more information, but the TLDR is that there are slight differences in the renderer used in Finder (Hydra Storm) and the renderer used in Reality Composer Pro (RealityKit), and these differences are causing your USDA to look correct in Finder while looking gray in RCP. However! Your USDA file looks strange, and there are things you can do to fix it. It looks like you've merged a physics material with a rendering material, and the physics fields are causing the material to break in Reality Composer Pro (but don't break in Finder). I'm not sure how you generated this USDA file (did you edit it by hand?) but try replacing the block starting with def Material material ( with this code, which is simpler: def Material material { token outp
2w
Reply to Having trouble with USD material not showing correct color
This is the usda file for the asset. There is a diffuse color listed in the Shader but it appears RealityKit only registers the default color of (0.18, 0.18, 0.18) (from here https://openusd.org/dev/spec_usdpreviewsurface.html) ( defaultPrim = Root upAxis = Z ) def Xform Root { def Xform Red_block ( apiSchemas = [PhysicsMassAPI, PhysicsRigidBodyAPI, PhysxRigidBodyAPI] ) { float physics:mass = 1 bool physxRigidBody:disableGravity = 0 bool physxRigidBody:retainAccelerations = 0 token ui:displayGroup = Material Graphs token ui:displayName = Red_block int ui:order = 1024 float3 xformOp:rotateXYZ = (0, -0, 0) float3 xformOp:scale = (1, 1, 1) double3 xformOp:translate = (0, 0, 0) uniform token[] xformOpOrder = [xformOp:translate, xformOp:rotateXYZ, xformOp:scale] def geometry { def Cube mesh ( apiSchemas = [PhysicsCollisionAPI, PhysxCollisionAPI, MaterialBindingAPI] ) { rel material:binding = ( bindMaterialAs = strongerThanDescendants ) rel material:binding:physics = ( bindMaterialAs = strongerThanDescen
2w
Reply to Declared Age Range: How to support age verification on iOS < 26?
This is not legal advice, nor a statement from Apple. I will share what I'm going to do in my apps and recommend to others. How I interpret 121.056 (B) (1) is basically, use the signals when they're available. If they're not available, you can't use them. You can't do the impossible. So if you have an app update that supports iOS 26, implement it there, and < 26 you simply can't. As a developer, it is impossible to use the age signals provided by the App Store if they don't exist. If you're not comfortable with this approach, file feedback asking for support on devices < 26. Hypothetically, if Apple were to add support to, say iOS 18, it would still be something like iOS 18.8.x or higher. I am closely following the OS Usage page and waiting for an update to show the adoption of 26. https://developer.apple.com/support/app-store/ For my specific usage, I'm moving my apps to 26+ for my updates. However, I have apps that include watch extensions, and an Apple Vision Pro target. This presents its ow
2w