Re: Code-signing oddness
Re: Code-signing oddness
- Subject: Re: Code-signing oddness
- From: Shane Stanley <email@hidden>
- Date: Wed, 07 May 2014 17:22:32 +1000
On 7 May 2014, at 5:03 pm, Quincey Morris <email@hidden> wrote:
> First of all, I suggest you try going to the Code Signing section of the build settings, and remove all the *target level* settings that are there. Perhaps also the project-level settings, if they have been customized somewhere in the project’s past.
OK, I've just created a new project. I'm assuming the Build Settings default is Don't Code Sign; no default appears in the OS X Default column of Build Settings unless I select it. At any rate, I haven't changed any build setting. (This is Xcode 5.1.1, BTW.)
>
> Then, go back to the General tab, and choose Developer ID or Mac App Store, according to the distribution method you plan to use, *and* choose the team under which the distribution is to occur. If Xcode reports an error under the team name, use the “Fix” button.
I've chosen Developer ID, then Team Shane Stanley (the only team). As I mentioned, in System Preferences -> Profiles, this team has the Application ID matching that of my Developer ID.
>
> After that, things should work normally, and you shouldn’t have to go back to the Code Signing section of build settings at all.
So I build, and the transcript says:
Using code signing identity "Mac Developer: Shane Stanley (XXXXXX)"
That's the wrong one, with a different ID.
> If that doesn’t produce the correct code signing behavior, or if you can’t fix the reported error, then likely Xcode is stymied because there are still some archeological build settings that it doesn’t recognize, or perhaps because your developer account information is incomplete or ambiguous. In that case, I *strongly* suggest you call Developer Program Support (I say again, Developer *Program* Support, which is something entirely different from Developer *Technical* Support) on their convenient toll-free number. Their job is to make sure you can use the developer program membership that you paid for, and are currently unable to use for code signing. So let them do their job and stop punishing yourself.
I understand what you're saying, but this looks more like a simple Xcode bug to me. But if it doesn't happen to anyone else, then there's clearly more to it.
--
Shane Stanley <email@hidden>
<www.macosxautomation.com/applescript/apps/>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden