Apple Maps Guides

Thanks for the post. We appreciate your interest in participating in the forums! These forums are for questions about developing software and accessories for Apple platforms. Your question seems related to Apple Developer membership. I would recommend to check this help page for the renewal of the membership as its automatic as far as I know: https://developer.apple.com/help/account/membership/renewal/ Albert Pascual
  Worldwide Developer Relations.

@pcfist Thanks for the confirmation. I'll give it a try when I get a chance. Unfortunately I am spending most of my time finding and reporting macOS/iPadOS/iOS 26 bugs that are impacting my app. Then I waste time trying to find work arounds since Apple isn't fixing any of the issues.

This issue is also affecting existing apps built with Xcode prior to 26 and a base SDK prior to 26 but being run on macOS 26. So clearly it's a framework issue in macOS 26 that is affecting an app no matter how/when it was built. It just needs to be an app using Scaled to Match iPad. I really hope Apple gets this resolved in macOS 26.1 (along with half a dozen other critical functionality bugs that I've reported and still are not fixed).

Update: Still locked out — no delete button, in-app purchase panel unresponsive, and new version option missing. Cache cleared, multiple browsers tested, still frozen. Case ID 102715606681. Apple please escalate — this is blocking submission.

We appreciate your interest in participating in the forums! These forums are for questions about developing software and accessories for Apple platforms. Your question seems related to a consumer feature and is better suited for the Apple Support Communities https://discussions.apple.com/welcome I would recommend to provide the support team more information about what version of iOS did you update to. Albert Pascual
  Worldwide Developer Relations.

If you run codesign on your executable, it tells you exactly what the problem is: /tmp $ codesign -vv -R=anchor apple generic renderrob.app renderrob.app: unsealed contents present in the root directory of an embedded framework In subcomponent: /private/tmp/renderrob.app/Contents/Frameworks/Python.framework If you explore that framework using Terminal, you'll see what it's complaining about: /tmp $ find /private/tmp/renderrob.app/Contents/Frameworks/Python.framework ... /private/tmp/renderrob.app/Contents/Frameworks/Python.framework/Versions/._Current /private/tmp/renderrob.app/Contents/Frameworks/Python.framework/._Resources /private/tmp/renderrob.app/Contents/Frameworks/Python.framework/._Python Remove those files and try again: /tmp $ rm /private/tmp/renderrob.app/Contents/Frameworks/Python.framework/Versions/._Current /tmp $ rm /private/tmp/renderrob.app/Contents/Frameworks/Python.framework/._Resources /tmp $ rm /private/tmp/renderrob.app/Contents/Frameworks/Python.framework/._Python /tmp $ codes

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