Well, I've not had codesigning issues for a long while but I have now had a new one on me. Its a warning, not a fail :- Application failed codesign verification. The signature was invalid, contains disallowed entitlements, or it was not signed with an iPhone Distribution Certificate. (-19011) So, it validates fine and has been submitted to apple with no issues found! Interesting to see what happens at the other end. Possibly down to have a long name but not sure. Anyone else seen anything like this?

I wish I documented some of the codesign errors I've seen so I could tell you straight up, but it might be something to do with leaving your dev cert in when creating the archive or something similar. It doesn't sound good that you submitted something that says it wasn't signed by a Dist cert. I do remember once submitting something that made it past the upload and said it had to issues, but it really did. I know none of the above might be much help, but I wish you luck with it.

Figured out the issue if anyone ever needs it. Basically my app name was too long. Due to this it cut off some of the code which I spotted on the output log after codesigning. The end of the code reads.. InstallationBuildProductsLocation/Applications/condescendingwonkawallpapers.app/embedded.mobil But should say .....embedded.mobileprovision Hopefully this will help anyone who may have the same issue.

Starting to keep a record of code signing issues...thanks for sharing! Mark

This one is quite remarkable. They dont specify that an app name has a limit on it, i worked out that 10 characters were missing so i needed to shorten it by at least that amount - It worked. Its a new one on me and its a particularly long app name. Moral of the story is keep the names short I think!