Brad, Yes, Xcode 6 breaks what used to be valid signing workflows under previous versions. Unfortunately, Apple’s documentation hasn’t caught up, and most of DTS is clueless on this subject. It took me literally months to get a useful answer. This BTW is not a bug, it is apparently as a result of Apple deliberately tightening up signing requirements.
In short, the only supported workflow now is “team based signing”. Apple is quite vague about what that really means, but in my case it involve setting Code Signing Identity to “Developer”, and Provisioning Profile to “Automatic”. Trying to override these settings with e.g., a specific profile, results in bad things happening. Sandy > On Feb 11, 2015, at 7:05 PM, Bradley O'Hearne <br...@bighillsoftware.com> > wrote: > > Hello, > > I am using Xcode 6.1.1 on OS X Yosemite and have exported an archive as a Mac > Installer Package using a Developer ID to sign it. The installer is created > successfully, and when run, the installer executes the installation > successfully. But when I attempt to launch the app, it crashes immediately, > with the following in the crash dump: > > Exception Type: EXC_CRASH (Code Signature Invalid) > Exception Codes: 0x0000000000000000, 0x0000000000000000 > > The problem is somehow with signing, though build settings in Xcode all > follow the documented approach to code signing using the proper Mac Developer > Program certificates. I have no errors or warnings when building the app. I > have no errors or warnings or problems launching and running the app in the > debugger. I also can export the same archive as a Developer ID-signed > Application and it exports, launches, and runs just fine. Additionally, this > is not something new I'm doing -- in previous development cycles (and earlier > in this one) I was able to successfully export as a Mac Installer Package and > run fine -- albeit that was on earlier versions of Xcode (and possibly OS X > too). > > In various other Internet-y places, I have found references to others having > this same problem recently, but none of those had any resolution. A couple of > posters commented that even after several weeks with communicating with Apple > DTS they still hadn't been given or were able to find a resolution. So I am > appealing to the community on the following points: > > Has anyone who has encountered this found a resolution to the problem? > Can anyone confirm this as a legitimate Xcode bug? > Any other suggestions to get around this? (Please note -- for reasons out of > my control, this app has to be distributed as a Developer ID-signed Mac > Installer Package -- we cannot distribute at this time through the Mac App > Store. Perhaps down the road, but not at this time). > > Your help is appreciated. This is a direct show-stopper for us being able to > ship our app to production. > > Thanks, > > Brad > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/cocoa-dev/mcguffogl%40gmail.com > > This email sent to mcguff...@gmail.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
