Text of developer.apple.com › forums › thread › 856903 as Styx crawled it on Nov 19, 2026. The page may have changed since. Only its words are kept, without pictures or layout.

Open the live page

Unexpected com.apple.macl extended… | Apple Developer Forums

Unexpected com.apple.macl extended attribute on macOS app bundle and provisioning profile Code Signing Certificates, Identifiers & Profiles You’re now watching this thread. If you’ve opted in to email or web notifications, you’ll be notified when there’s activity. Click again to stop watching or visit your profile to manage watched threads and notifications. You’ve stopped watching this thread and will no longer receive emails or web notifications when there’s activity.

Click again to start watching. JonaNorth OP Created 1w Replies 2 Boosts 0 Views 184 Participants 3 Hello, I'm investigating an unexpected com.apple.macl extended attribute while preparing a macOS application for Developer ID signing. I have observed the attribute in two places: On the root of an application bundle, where the recorded 72-byte attribute value changed during testing. On a Developer ID provisioning profile, where a 72-byte com.apple.macl value is present before signing.

I also created a minimal Xcode reproducer that independently demonstrated the unexpected attribute behavior. I have not established which process creates or modifies the attribute, or whether its presence affects code-signing integrity. My questions are: Is this expected macOS behavior for app bundles and provisioning profiles? What is the recommended supported method to identify which system component creates or modifies this attribute?

How should developers handle this situation when preparing and validating Developer ID signed applications? I would prefer to understand the cause rather than remove or suppress the attribute without knowing its security implications. Thank you. Replies 2 Boosts 0 Views 184 Participants 3 DTS Engineer OP Apple 1w Is this expected macOS behavior for app bundles and provisioning profiles? Yes. As Quinn noted here , it's tied to the mandatory access control (MAC) subsystem, which means it can end up being attached to nearly any object.

What is the recommended supported method to identify which system component creates or modifies this attribute? I'm not sure there is any good way to identify it's source, however, it's also not something there's any reason to actively dig into. How should developers handle this situation when preparing and validating Developer ID signed applications? If you're creating the object you're specifically going to distribute then you might want to delete it as part of "cleaning up" unnecessary metadata, but other than that I'd ignore it.

I have not established which process creates or modifies the attribute, or whether its presence affects code-signing integrity. It won't. Most extended attributes are ignored by the codesigning architecture, however, the larger issue is that the outermost directory of your app isn't really considered "part" of your app, at least not for code signing purposes. That is, in a hierarchy like this: MyApp.app Contents ... ...whatever is inside MyApp.app is considered "part" of the app (which is why you can't just add stuff beside "Contents"), but the MyApp.app directory ITSELF isn't really "part" of the app.

This is why things like renaming the app have no effect on code signing. __ Kevin Elliott DTS Engineer, CoreOS/Hardware Add comment DTS Engineer OP Apple 1w What Kevin said and… My experience is that this MAC xattr most commonly shows up in locations managed by MAC [1], Desktop, Documents, and so on. Locations like this are a very poor choice for your source code or build products. A better option is to store those inside non-special directories.

For example, you might store all your source code in a ~/Projects directory that you created. Oh, and don’t even think about putting such things on iCloud Drive (-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com" [1] For more details about what I mean by this, see On File System Permissions . Add comment