search

kgn / LaunchAtLoginHelper

A helper app to launch a main app at login under sandboxing
http://kgn.github.com/LaunchAtLoginHelper
MIT License
57 stars 13 forks source link

Code signing explanation #1

Open tomtaylor opened 12 years ago

tomtaylor commented 12 years ago

This looks great.

Can you explain about how you're handling provisioning profiles and code signing across the main application and the helper? Every combination I've tried seems to have a flaw.

kgn commented 12 years ago

Hmm I am not sure, I haven't run into issues with provisioning profiles on the Mac. I'll describe what I have setup which might help:

In Organizer for My Mac I only have one provisioning profile, which is Mac Team Provisioning Profile:

Then the code signing for my main project is:

And the code signing for LaunchAtLoginHelper app is unchanged and looks the same as in the screenshot above.

Hope this helps.

tomtaylor commented 12 years ago

Thanks - are the helper and the main application signed with the same key? Does your application pass Mac App Store validation?

kgn commented 12 years ago

Yes, I've submitted two apps that have been approved with this helper app:

tomtaylor commented 12 years ago

Thanks, that's good to know. I'm still a bit unsure about the code signing: did you use a separate provisioning profile on a separate bundle ID for the main app and the helper?

kgn commented 12 years ago

I used the same profile I think, I didn't have to do anything special with the provisioning profiles so I assume they both use the same one. Have you been able to submit the app yet?

codler commented 11 years ago

+1 Do you know if this work in mountain lion?

holgersindbaek commented 11 years ago

I'm getting this error when I submit my app to the app store, using the this otherwise awesome library:

Invalid Provisioning Profile Location - The provisioning profile for your Mac OS X app must be located in the

Contents directory of the main app bundle. A provisioning profile is optional, but you cannot submit more than one.

Anyone having any experience with that?

kgn commented 11 years ago

Hmm, I'm sorry to say that I have not submitted a new build to the app store in a while so I am not sure if anything has changed. Maybe make sure the same provisioning profiles are being used by your app and LaunchAtLoginHelper.

holgersindbaek commented 11 years ago

The same provisioning profile are being used.

I ended up solving it by removing the embedded profile in the helper app:

http://blog.mcohen.me/2012/05/20/sandboxing-revisited/

Doesn't seem like an optimal solution though.

kgn commented 11 years ago

Glad you found a solution! I'll have to investigate this more the next time I submit an update.

holgersindbaek commented 11 years ago

Would be awesome. It's the best launch helper I've found. Really nicely done!