I have tried everything that I can think of or find online and I keep getting an Invalid Signature error. I have a valid distribution certificate. It has a Provisioning Profile attatched to it that is the valid one for this app. I have the build settings Code Signing Identity set to this distribution certificate (‘iPhone Distribution: Valhalla Studios Bifrost’ in ‘Hot Tail Provisioning Profile’) so I don’t understand what I have missed here!
Can anyone help me understand how this is supposed to work. This is my first attempt at submitting an app.
Hi. I feel for you.
For me, I always seem to be trying to submit my projects when the distribution certificate has just expired on me. Code signing / certificate assigning, etc. is always a pain for me, and the least enjoyable part of the entire process - but then for me, xcode is a mystery.
One thing you might like to check, and something I have missed in the past, it that you have correctly assigned your Distribution certificate at the TARGET level (which override any values at the project level). Also, after the build, check the build log as the dev centre instructions suggest to confirm the existence of the the correct certificate.
If you are 100% certain your code signing settings are correct and valid, this is what Apple will suggest next:-
Choose “Clean All” in Xcode, delete the “build” directory in the Finder, and rebuild your release target.
Hope this helps, keep at it, you’ll get there…
I have tried all of those things, and then I set up some new certificates through the portal and tried that. So far, no change, same email sent to me intsantly every time.
The part about checking the build results is a little confusing. I am looking at them right now. I have two that refer to ProcessProductPackaging. One is about the Entitlements.plist and the other seems to be talking about embedding the mobileprovision. But the folders they go to are different. I don’t know what they should be.
The mobileprovision process is refering to /build/HotTail.app/embedded.mobileprovision (this is where the .app is)
The Entitlements.plist refers to /build/Unity-iPhone.build/Distribution-iphoneos/Unity-iPhone.build/HotTail.xcent
this doesn’t seem right to me. That last path definately sounds wrong, but I don’t know where that was generated or how, so I’m not sure how to fix it, or what it should be. I also read a few times about looking at the project.pbxproj and looking at the distribution build section. In here are a couple of sections on PROVISIONING_PROFILE that according to some threads should have by provisioning profiles identifier in there, but on mine they are all empty strings. I have tried manually saving the identifier in but it didn’t change the error when submitting.
All in all it feels like something is wrong, but I don’t understand the process well enough to be able to deduce what it is. I really need help here.
It seems I got it working. The new provisioning profile i set up had an app id of .com.. and I had followed the directions of a thread explaining to add a new line to the Entitlements.plist for the application-identifier and I only had com.. I just needed to add the provision seed to the front of that and it worked.
Ok, awesome. Not working again. I am trying to submit an update. Something that you would think would be very simple. But after taking a week to get it to allow an armv7 only build again, I am now getting the magic invalid signature email after submitting. Nothing has changed so I can’t figure out what is wrong.
I was reading this post
http://www.iphonedevsdk.com/forum/iphone-sdk-development/14023-binary-you-uploaded-invalid-signature-invalid-not-signed.html
and it says something about needing a new app id? is this correct? the bundle identifier for my version 1.0 was as above. .com.. but this post is saying that that is the problem. Surely I don’t need a new app id everytime I want to update
Adsy, i have a problem just like you. i’ ve upload my apps for 6 time and still got error Invalid Signature. i don’t know what to do now