EPM-M macOS Golden Gate Known issues
UPDATED: 24th September 2026
With macOS Golden Gate being announced in WWDC, I thought I'd create a post to share any known issues we've found so far.
We have been testing EPM with all macOS Golden Gate betas which we have available to us as a member of the Apple Developer Program. During this testing, we’ve identified a few minor issues. Below, you’ll find details of the problems, workarounds (where available), and planned resolutions.
Issue 1: Incorrect OS Name and Version Displayed in PM Cloud
- Description: In PM Cloud, the macOS Golden Gate version is reported incorrectly.
- Where to See: Home → Computer → Details → OS → the “Name” and “Version” fields show incorrect values.
- Workaround: None.
- Resolution: This will be fixed in 26.3.2 release, where the OS will correctly display as macOS Golden Gate (27.0).
Issue 2: Apple Publisher Name Change for macOS 27 System Applications
- Description: In macOS 27 Golden Gate, Apple has changed the code-signing publisher name for system applications from "Software signing" to "macOS Software Signing". Any EPM policies using publisher-based application rules targeting Apple system apps may no longer match correctly.
- Where to See: Policy rules using publisher matching for Apple system applications, affected rules will fail to match on macOS 27 endpoints.
- Workaround: Update your existing policies to add matching criteria with the new value “macOS Software Signing",
- Resolution: still investigating the best solution
Issue 3: Users unable to remove applications from /Applications
- Description: In macOS 27 Golden Gate, Apple has changed the DesktopServices to root access when removing applications from /Applications.
- Where to See: Policy rules allowing standard users to remove applications from /Applications by moving the application to The Bin, the user will see an Admin prompt.
- Workaround: None
- Resolution: Resolved as part of 26.3.2 (Planned Late September / Early October)
