[Resolved] Your application built but failed to pass Apple's validation tests

Getting Started Newbie Questions
#1

I built my game for app store distribution, submitted it and it was accepted. Now when I build the same exact code (as far as I know) with my original Development provisioning profile, I get the message:

Your application built but failed to pass Apple's validation tests.

Your application cannot be uploaded to the App Store until it passes Apple's validation tests, 
though you may install it directly to provisioned devices.

Executable=/Users/mike/Documents/lua-builds/Catch'em.app/Catch'em
codesign\_wrapper-0.7.10: using Apple CA for profile evaluation

I have not changed the Corona SDK, Xcode or OS. Using Build 704 of Corona.

I am a loss what this means and how to address it. This problem does occur if I use the app store distribution profile.

Thanks,
Mike [import]uid: 101075 topic_id: 22661 reply_id: 322661[/import]

#2

Same here. What’s important though is that when you build using the app store distribution certificate you don’t get the error (at least I don’t). I only get this when I build with my development certificate for my phone… and the error doesn’t stop me from loading it on my phone for testing.
It is strange how this only showed up after submitting a version to the app store. I don’t think its anything to worry about… I hope : )
Tim
interAlia LLC [import]uid: 129205 topic_id: 22661 reply_id: 90395[/import]

#3

Check provisioning profile carefully, that it isn’t expired, etc. - you can also view it in Xcode to see if there are any warnings, which can be useful. [import]uid: 52491 topic_id: 22661 reply_id: 90416[/import]

#4

My provisioning profile does not expire until January 2013. Any other ideas? Using Build 704.

I deleted the sandbox folder (since I don’t understand the build process) with the same results.

The Corona Terminal has this after the build. Does it mean something relevant to this issue?

/Users/mike/Documents/lua-builds/Catch’em.app: replacing invalid existing signature
/Users/mike/Documents/lua-builds/Catch’em.app: signed bundle with Mach-O universal (armv6 armv7) [com.badmonkeygames.catchem]

I also downloaded and installed my code signing certificate again from the provisioning portal and the problem persists.

Mike [import]uid: 101075 topic_id: 22661 reply_id: 92644[/import]

#5

Would it have something to do because of the " ****" symbol that youre using in the name of the app? :\

Just trying to investigate.
Cheers,
Rodrigo. [import]uid: 89165 topic_id: 22661 reply_id: 92651[/import]

#6

Nice catch Rodrigo - that is worth trying to remove and test build.

Also, to check your profiles and certificates you should build one of our sample apps; if you get no errors then you know these are find and it’s specific to your project, which isolates things. :slight_smile: [import]uid: 52491 topic_id: 22661 reply_id: 92698[/import]

#7

I’m joining this thread because I’m having the same problem (I had joined this thread but not quite the same issues - http://developer.anscamobile.com/forum/2012/01/02/bundle-ids-dots-are-being-replaced-and-being-rejected-uploader)

I’m getting

warning: Application failed codesign verification.
The signature was invalid, or it was not signed with an
iPhone Distribution Certificate. (-19011)

Using 2011.704 (was .591). Since Feb 28th I’m getting this error with code and provisioning profile that was working and is unchanged since Feb 28th. Have tried the following.

  1. Created new provisioning profile
  2. Used ‘hello world’ app to test, same problem.

I’m using macincloud, which has xcode 4.2.1
Not using bundle ID because I’m months from app store submission.
Using development, not distribution cert obviously. [import]uid: 120570 topic_id: 22661 reply_id: 92716[/import]

#8

Are you able to install the app on your device anyway via Xcode, or do you get an error then also? [import]uid: 52491 topic_id: 22661 reply_id: 92726[/import]

#9

Using windows for dev. Macinacloud for mac, so cant install from xcode.
Install fails on windows. [import]uid: 120570 topic_id: 22661 reply_id: 92732[/import]

#10

Running out of ideas here. Just tried downloading provisioning profile directly on macincloud, instead of downloading on windows and drop-boxing to macincloud. Installed into xcode.
Still same error. [import]uid: 120570 topic_id: 22661 reply_id: 92789[/import]

#11

@conor1, read it below and see if it can give you some “light”.

I’ve encountered the same problem too (error iPhone Distribution Certificate. (-19011)). It showed that I had a duplicate certificate registration in my keychains. Removing one of them (I removed the one from my system keychain) fixed the problem.

Steps that helped me to resolve my problem:

Open KeyChain Access application
Select the ‘login’ keychain, and select in the bottom pane ‘Certificates’
Switch to the ‘system’ keychain and see if there are certificates registered in both chains.
Remove one of them
Rebuild the application

I hope that helps.

Cheers,
Rodrigo.
[import]uid: 89165 topic_id: 22661 reply_id: 92804[/import]

#12

Seems on macincloud I can’t access keychain. Going to ask them.
Still love to know what’s changed in last 2 weeks. [import]uid: 120570 topic_id: 22661 reply_id: 92846[/import]

#13

I originally built with the quote character, but removed it and still have the problem. Built the SimplePoolPlus (iPhone only) and have the same problem. This means that either my version of the Corona SDK (build 704) is not compatible with whatever is running on the server, or my provisioning profile/certificates are messed up. None of these have changed as far as I know.

I associate this issue coming up with building for the app store, but cannot say for sure.

Is there a trouble shooting guide for me to verify the provisioning profile is good (looks ok in Xcode already) and the certificate are valid or if there is something on my key chain now that is messing things up?

Thanks,
Mike [import]uid: 101075 topic_id: 22661 reply_id: 92898[/import]

#14

If you cannot build the sample code then chances are it is an issue with certificates.

To confirm, what version of Xcode are you using?

If all else fails you may want to remove all certificates and provisioning profiles and recreate them - we do have a walkthrough for creating in the Device Builds sub forum. [import]uid: 52491 topic_id: 22661 reply_id: 92933[/import]

#15

I’ve just deleted then reinstalled my certificate and my provisioning profile. I also removed my distribution certificate from the machine (used for published app with another sdk).

Did manage to get access to keychain.

I’m still getting this

warning: Application failed codesign verification. The signature was invalid, contains disallowed entitlements, or it was not signed with an iPhone Distribution Certificate. (-19011)
Executable=/Users/user205/Desktop/corona/maze30.app/maze30
codesign_wrapper-0.7.10: using Apple CA for profile evaluation

I keep going back to this: what has changed since end February? [import]uid: 120570 topic_id: 22661 reply_id: 92972[/import]

#16

@peach pellen
Have same problem. Yesterday there was no such message (“using Apple CA for profile evaluation”), my certificates are valid.
Any further ideas except “issue with certificates” and “’ in the name”? [import]uid: 9058 topic_id: 22661 reply_id: 93004[/import]

#17

My version for Xcode is 4.1, and it has not changed. I believe that I have not changed anything since submitting my app to the Apple app store in late February. Something happened near the end of February and from the other responses on this thread, I am not the only one (not meant to be accusing anyone of something, just trying to offer alternative debug paths for us).

I will try to remove and recreate the provisioning profile and certificate.

Should I try upgrading my version of Corona? I am currently using build 704, and I am not sure it is advised to release to the app store with a more recent build.

Mike [import]uid: 101075 topic_id: 22661 reply_id: 93015[/import]

#18

>>>>near the end of February<<<<

I believe this is key, either in Apple process or in Corona process, not the downloaded software. [import]uid: 120570 topic_id: 22661 reply_id: 93016[/import]

#19

I am so frustrated by all of this. It may not even be Ansca problem, but I can’t use this software if I can’t even test my app (since end February) on an Apple device.
I use another SDK for phone only stuff, because of the ARM6 issue. I’d love to use Corona for everything but I can’t. Easy to use and understand, but I can only use it for tablets.

I do everything on Windows. The other sdk requires me to use a Mac only for App Store upload, everything else on a PC. Compile the App on the pc, no server required, then use IPCU to add the app to my IOS devices for testing.

On Monday week I have 2 students starting work on apps and I want them to use Corona. However I may have to get them to go the C++ route and abandon Corona. [import]uid: 120570 topic_id: 22661 reply_id: 93196[/import]

#20

I have built both for the store and AdHoc (and assisted others with store builds) over 20 times in the past fortnight - I haven’t run into any issues at all.

All three of you - who has previously built successfully? Has anything at all changed? Xcode version, Corona version, certificates, etc.?

If you have built before can you build that app again successfully using the same provisioning profile?

Please try to think of ANY changes you may have made, to your phone, your computer, Xcode, Corona, etc - no matter how insignificant they might seem.

This issue, whatever the cause, is not wide spread and so it’s important to get as much information as possible in order to try and isolate it. If someone can replicate it then we’re half way to a solution. (I’m happy to mess around with my setup but I need something to go on.)

Sharing other information in a detailed little post, like;

OS: Lion 10.7.3
Corona: 704
Xcode: 4.2

etc. is also helpful here.

Lastly, anyone using sub folders in their project can you please list all sub folder names here? We are aware of issues caused by using a sub folder and naming it “Resources” (this returns a signing error) however there may be other reserved names we have yet to encounter as issues.

Thank you for any and all info you can provide,
Peach :slight_smile:

[import]uid: 52491 topic_id: 22661 reply_id: 93208[/import]