Home/ Questions/Q 6689183
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T05:29:24+00:00

I have my Mac Developer: … certificate installed and it is valid. I have

  • 0

I have my “Mac Developer: …” certificate installed and it is valid.
I have the Apple Worldwide Developer Relations intermediate ceritficate as well.
I also have a “3rd Party Mac Developer Application” distribution certificate.

In my build settings I have chosen my “Mac Developer: …” identity for code-signing.
When I built the first time, codesign asked for permission to sign my app and I clicked Always Allow.

Then I did a “Show in Finder..” to see the Product of the build. I found my .app and double clicked it. However, this is what is shown in the system Console:

10/13/11 8:40:44.531 PM storeagent: Unsigned app (/Users/kenny/Library/Developer/Xcode/DerivedData/MyAppName-gabpxiaypxtnikelsyzjwkperixq/Build/Products/Debug/MyAppName.app).

I’m not running the app from Xcode, I just opened the Console app and then double-clicked the app in my build directory.

Why is my app still unsigned? What am I missing?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It took me a long time to figure out what was causing this when I had the same issue myself a while back. I finally figured it out. You must set the Code Signing Identity (in your app’s target & project settings) to 3rd Party mac Developer Application. Then, when exporting your app you must select the 3rd Party Mac Developer Installer certificate in the export wizard.

    That’s the only way that worked for me. Please correct me if I’m wrong.

    • 0