I have a script that prepares my app for the app store, and it works perfectly until I include entitlements. Then, after creating the package and installing, my app launches and quits, but never gives me the login for the app store. If I remove the entitlements, it works fine.
My question is, do I have to register my entitlements with the app store before the app will work? (I’m especially perplexed because, when I first tried it with the entitlements, it worked just fine.)
dim initialSignCmd as string = "/usr/bin/codesign --force -s " + certApp + " " + pathAppName
if kIncludeEntitlements and entitlementsPath <> "" then
initialSignCmd = initialSignCmd + " --entitlement " + entitlementsPath
end if
Your entitlements looks fine. You didn’t have to register entitlements with Apple a couple of weeks ago, but then they do changes things frequently and without warning.
Try manually code signing in the terminal, just to see if there are any errors being reported. The error message in the console sorta suggests to me that it’s failing somehow.
Then other thing to try is to delete the application container in your library folder, these can get corrupted and release a whole world of woe.
Lastly, try using a wrapping application to code sign and wrap your application, if it works in a wrapping app, it should give you some indication as to where to look in your script.
Also - how are you testing installation? Although you can double-click the PKG file I think that’s not the correct way to do it, you actually are supposed to use the terminal :
To answer some of the questions, I have AppWrapperMini (excellent), but not AppWrapper. No matter, I’m comfortable in the CLI so I just needed the right commands.
And yes, installing through the CLI as recommended. Michael, if you see the comment when you run “sudo installer”, it actually advises you to run as admin, not root, so just use “installer” and it will ask you for your password anyway. (I’m not sure if that’s a change from previous versions of the OS.)
I’m on MacOS X 10.8.4. using Xojo 2013r2.
I am also using additional plugins since I first tried this so I am going to see what happens if I take those out of the mix.
Thanks for all the comments and suggestions. I am going to devote some serious time to it today and will report back what I find.
[quote=23688:@Kem Tekinay]Michael, if you see the comment when you run “sudo installer”, it actually advises you to run as admin, not root, so just use “installer” and it will ask you for your password anyway. (I’m not sure if that’s a change from previous versions of the OS.)
[/quote]
That does sound different, and my advice is definitely from when I was testing in 10.6. That’s good to know that it’s not the same in 10.8.
I’m testing on a different machine now, but it’s working, so I have to chalk it up to the typo. And that makes sense if I included the “s” in my script’s initial versions and screwed it up later.