Apple Maps Guides

Hello Apple Developer Support Team, I’m facing an issue stapling notarization tickets to my signed macOS installer package (.pkg). What I’ve done so far: Code-signed my .app with Developer ID certificate. Created a signed installer package (.pkg) using pkgbuild. Submitted the package to Apple notarization via xcrun notarytool submit ... --wait. Status: Accepted. Tried stapling using xcrun stapler staple -v IPMPlus_Arm_Installer_signed.pkg, but it fails with Error 65. xcrun stapler validate reports no ticket stapled. Observations: Curl tests to CloudKit endpoints return 404 or NOT_FOUND errors. Port 443 connectivity to api.apple-cloudkit.com and gs.apple.com works. Retried stapling from multiple networks, including a mobile hotspot. Same result. System time is synced; package signature is valid (pkgutil --check-signature). Questions: Is this a known issue with stapler / CloudKit endpoints? Is there a workaround to successfully staple a notarization ticket to a signed .pkg? Any guidance would

Hi Smith, To add more context to my previous reply, especially regarding the userclient-access entitlement: The main reason we switched our testing focus to the communicates-with-drivers entitlement is because the userclient-access path is completely blocked at build time for us, exactly as you suspected. Here is a detailed breakdown of what happens when we use userclient-access: Entitlement Configuration: We configure our DriverKitSampleApp.entitlements with the correct, specific bundle ID of our DEXT: com.apple.developer.driverkit.userclient-access com.accusys.Acxxx.driver Immediate Build Failure: As soon as we try to build the app with this entitlement, Xcode's signing process fails instantly. This happens with both Automatic Signing and a manually created Provisioning Profile. The Error Message: The error is always the same: Provisioning profile ... doesn't match the entitlements file's value for the com.apple.developer.driverkit.userclient-access entitlement. The Proof (from QuickLook): Following your

Predictive code completion in Xcode uses a model trained specifically for Swift and Apple SDKs. It is a productivity feature to help you while writing code in Xcode — it is not part of the Apple SDK where you can invoke it from your app's code. — Ed Ford,  DTS Engineer

My code is much more elaborate than that. To start with, I create my own print operation via printOperationWithSettings:error: (still Objective-C). I don't call runModal at all. WebView is really tricky with printing, at least for me. I create a new view just for printing, then load it, and print in my load completion using NSDocument's printDocumentWithSettings:.... And of course, all this still uses the long-deprecated WebView class. I don't know if Apple ever added print support WKWebView. Still works in Tahoe. You seem to be trying to use the new logic. I don't plan on using WKWebView in the future anyway. So if Apple eventually removes the old WebView I won't be affected.

This is not working for me on Xcode 16.4. How is this still broken? Does Apple not have tests for their testing features? Are there any workarounds that can be provided?

FYI - none of these issues have been resolved as of iOS/iPadOS 26.1 beta 2. Dear Apple, please fix all of these scope button issues. They are impacting my app. If you do not intend to fix these then you should mark the APIs as deprecated and suggest an alternate solution.

Could you please provide more information about the issue? Are you able to narrow the issue to a specific API and which OS version are you testing? For additional tips on creating effective Apple Developer Forums posts, refer to the tips on writing forums posts.