LaunchAtLoginHelper icon indicating copy to clipboard operation
LaunchAtLoginHelper copied to clipboard

Code signing explanation

Open tomtaylor opened this issue 13 years ago • 11 comments

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.

tomtaylor avatar May 20 '12 19:05 tomtaylor

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.

kgn avatar May 20 '12 19:05 kgn

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

tomtaylor avatar May 21 '12 21:05 tomtaylor

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

kgn avatar May 21 '12 21:05 kgn

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?

tomtaylor avatar May 21 '12 21:05 tomtaylor

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?

kgn avatar May 26 '12 16:05 kgn

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

codler avatar Aug 29 '12 20:08 codler

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?

holgersindbaek avatar Apr 17 '13 02:04 holgersindbaek

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.

kgn avatar Apr 17 '13 20:04 kgn

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.

holgersindbaek avatar Apr 17 '13 20:04 holgersindbaek

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

kgn avatar Apr 17 '13 21:04 kgn

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

holgersindbaek avatar Apr 17 '13 21:04 holgersindbaek