Re: Code signing issues
Re: Code signing issues
- Subject: Re: Code signing issues
- From: Gideon King <email@hidden>
- Date: Tue, 18 Oct 2011 10:19:37 +1000
Thanks for the reply Graham. I'm using Xcode 4.2. Please see comments inline
On 18/10/2011, at 9:55 AM, Graham Cox wrote:
> On 18/10/2011, at 10:34 AM, Gideon King wrote:
>
>> So I have the following questions:
>>
>> 1. When creating the certificates, 3 certs are created and added to the keychain - should I be able to see all three of them in Xcode? If so, what do I need to do to get them to show up there?
>
> In the build settings, only one cert shows up, '3rd Party Mac Developer Application'. You can choose 'Other…' and type one in, but I have never needed to do this.
OK, not sure why have three certs if only one ever shows up, but if always using the '3rd Party Mac Developer Application' for all your builds works for you, I'll try the same.
>
>
>> 2. When I do a build using my "Mac Developer" cert, it doesn't give any errors when signing, but the Store seems to think that the app is not signed. What do I do about this?
>
> At what stage does the Store "think" it isn't signed? I do "Archive" (in Xcode 3.x this was "Build & Archive"), then in the Organiser I click 'Validate'. The Organizer should package the app and sign the package using the '3rd Party Mac Developer Installer' cert. If you click 'Share' you can see this cert in the 'Identity' pop-up. Using this, you can create the signed package on disk and test the installation without having to attempt a submission to the Store.
I haven't got my head around the whole archive thing yet (or the Organizer for that matter). Perhaps this is something I need to look into next - I started looking at the documentation before but just got confused as to the purpose of the organizer and the build and archive options. I have just been building using Command+R and running the app from the Finder. So when I do that, the first time it tries to run, it finds that there is no receipt, and launch services (or whatever it is that handles this behind the scenes) must ask the store for a receipt, but it says it can't do so because the app is not signed.
>
>> 3. When I sign with my "3rd Party Mac Developer Application", I get the message about it not being a test user account, and to create an account in the sandbox. Is this something I need to do in the App store, in my development settings, a different Apple ID, or on my computer?
>
>
> I have no idea about this, sorry. Never seen it myself.
>
> Sounds like you might not have the installer certificate set up - it's separate and different from the app cert. You also need the WWDC cert, I'm not sure exactly where that comes into play, it needs to be in the keychain but it's never directly used at any step of the deployment procedure.
Yes, I have an installer cert, and have just installed the WWDR cert, but that didn't seem to make any difference.
Also, I'm worried about the CFBundleShortVersionString that is used for validation of the receipt. As every update will have a different version string, but the receipt will presumably have been created for the version that the user initially purchased, will this still work? Will they get an updated receipt when they download a new version of the app from the store?
Thanks again
Gideon
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden