Keep getting this message:
“package was signed with a certificate that is not valid for store submission.”
But I’ve installed both the certificates for the installer and the app, and applied them via the terminal as instructed on this post:
http://forum.unity3d.com/threads/71340-Submit-Unity-games-to-the-Mac-App-Store!
Other than starting over from scratch, not sure what to try next.
It is the saying the Certificate you are using does not give you right to put it on the App store. Apple requires you to have a Certificate from them that at least when I was doing it a few years ago cost about $100.00 for one type. This you may need to check with apple to make sure the certificate is valid though it might be and Apple is just having problems reading it. I remember having a problem trying to get something to go but do not remember how I fixed it. I think I just re downloaded the Certificate
I’ve already tried revoking, reissuing, and re-downloading the certificates, rebuilding the app, creating a new app id and new provisioning profile, yet the problem remains.
Only thing left is complain to apple tell a solution is found. There may be other things but I am not sure what.
I don’t know exactly, but I think you need to sign it with a “distribution profile” IIRC when you make the .app for mac store submission. So perhaps you are using the developer profile instead.
You’ll definitely be better off searching the Apple developer forum - there are tonnes of cases and solutions detailed there for these sorts of issues. You should be able to just sign right in using your existing iTunes Connect account.
The certificate creation process had been broken since the 14 for all dev centers. Today all provisioning portals and dev centers were down fixing this issue until around 7:30 EST (GMT -5:00). I was having trouble submitting to the iPhone app store, but got it after revoking all distribution certificates and profiles, removing them from keychain access, recreating them and installing them. Try starting fresh with your certificates and provisioning profiles.
Thanks for the heads up, I’ll try again tomorrow. Don’t have the patience for it tonight…
No problem. If you read through deforms.apple.com you’ll probably see a lot of people with the same situation as you.
That did indeed fix the first error, but now I’ve got:
When developing for iOS, you can manually change the bundle identifier in Unity, I guess you can’t do this when building to Mac store. I’m wondering if Unity might be using ‘unity.companyName.productName’ instead?
Okay, seems to be submitting now.
I recreated the Profile and tweaked the CFBundleIdentifier and CFBundleSignature in the info.plist to make sure they match.
Of course now I’ve received this from Apple: