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

Getting Started Newbie Questions
#21

As my mac is a macincloud, I’m happy to let you have access to it and see what’s there. In my case, there is still a project there unchanged since end Feb. Here are the facts

I have no sub-folders.
Everything developed on PC and transferred to macincloud.
3 projects successfully built Feb 26-28, no errors. Apps successfully transferred back to PC and placed on iPad and run as expected.
These projects are all concept tests, nowhere near completion.
No use made of camera, accelerometer or other devices on tablet.
Very similar to what might be done for Flash on PC, placing sprites, responding to touch, nothing complex.
Developer cert and provisioning profiles on macincloud

Macincloud had (and still has) Corona .591
Since installed .704, no difference
xcode 4.2.1
OSX 10.7.3

Screenshots of the xcode organiser are here showing my provisioning profiles and certificate. Citymaze is the unchanged app.

www.apptoonz.com/stuff/screenshot1.png
www.apptoonz.com/stuff/screenshot2.png [import]uid: 120570 topic_id: 22661 reply_id: 93235[/import]

#22

Hey Conor,

In your case Xcode seems to be looking for a Distribution certificate, as per the error you reported:
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

In Xcode I see no distribution certificate, only a developer one - could you try adding your distribution certificate to see if this makes a difference and let me know, please?

As far as accessing your mac goes, I’m not sure it would provide more use at this stage than the screenshots you provided (thank you) - however we will see what happens next. Ultimately the only thing I’d be looking for there is what certificates were installed and whether or not you had any warnings in Xcode, which you do not.

We will see what happens with the Distribution certificate installed :slight_smile: [import]uid: 52491 topic_id: 22661 reply_id: 93239[/import]

#23

These issues are usually caused by certificates as most people here have guessed. Check that you have a valid certificate in your keychain as apple have a habit of invalidating them when they do any of the following.

A) Have a policy change in the EULA.
B) Have changed a contract clause and require you to re-accept it.
C) You re-new your developer subscription.

You will likely need to visit the dev portal, check that none of the above has occured (I had to accept a new contract and was strangely asked a yes/no question about if I had a game in dispute).

Re-generate your certificates and re-download them. Delete old certificates from keychain. Then install the new ones and re-build your app.

This should remove the validation messages. [import]uid: 82631 topic_id: 22661 reply_id: 93245[/import]

#24

@peach

Finally got the distribution certificate into xcode. This stuff is such a pain (not your fault).

Now that I have that done I can’t build using the distribution cert because Corona doesn’t allow that in trial.

Seems Apple have changed something because a developer cert was enough prior to Feb 28 to allow Corona trial build the app for adhoc.

Now it seems we need distribution cert and associated prov prof (which is ad hoc, I checked again) but Corona trial can’t work with it.

So I’m in a bind. Don’t know if I can build apps, don’t know whether to take out subscription, don’t know whether to abandon.
Obviously need to pay subscription sometime, but in startup mode and trying to delay expenses until I have a product ready. [import]uid: 120570 topic_id: 22661 reply_id: 93249[/import]

#25

@peach pellen
It’s not issue with Distribute certificates, as it appears almost in one day at many developers.
We have Distribution Certificates installed and not expired!
I mention the only thing changed on my Mac before this issue is updated Application Loader (to 2.5.1), anything else was the same. [import]uid: 9058 topic_id: 22661 reply_id: 93257[/import]

#26

@Andriy

Are you saying that with a subscription paid you are having the same failure? So if I pay my subscription I will still have a problem?

Are you getting the same error?

warning: Application failed codesign verification. The signature was invalid, contains disallowed entitlements, or it was not signed with an iPhone Distribution Certificate. (-19011) [import]uid: 120570 topic_id: 22661 reply_id: 93259[/import]

#27

Andriy - I am not saying it’s an issue with Distibution certificates, the build process is saying that. I’m simply reporting.

What is your error?

Conor - the way I read your problem was that there was a possibility Apple was seeing the AdHoc as needing a distribution certificate and not a developer one - can you log into the dev center and see which profiles appear under dist and which under dev? I’m wondering if something has happened there.

I have seen this error occur in the past where the app can still be loaded onto device via Xcode but it’s hard to say with this stuff; Apple does NOT make certificate stuff easy. (As you mentioned, Conor.)

As mentioned above also make sure you haven’t missed any agreement updates that need accepting.

Peach :slight_smile:

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

#28

Peach,

I already had profiles under dev. Had to create new one under dist using different name in order to work with distribution cert.

I can’t do the xcode loading due to using macincloud.

Anyway I can’t test using distribution cert because I’m using trial, and I have no confidence after reading Andriy that I won’t still have the problem if I purchase now.

Do you want to give me a temporary subscription so I can see what happens? [import]uid: 120570 topic_id: 22661 reply_id: 93477[/import]

#29

Further update

I decided to delete my developer certificate and start again. Reason is the cert was created via Marmalade tool ‘iPhone Sign Request’. Their tool means you can avoid using a Mac until time to upload to App Store. Worked fine, no problem when I had an App to submit.
Created a new cert on macincloud, uploaded to xcode and Provisioning Portal. Created new developer prov prof and went at the build again. Still same error.

So it’s not the certificate. [import]uid: 120570 topic_id: 22661 reply_id: 93485[/import]

#30

@Conor - It’s something that can happen to anyone, subscriber or not - certificates, profiles, etc. - Apple does have this set up in a really, really frustrating way. Things break for seemingly no reason. So yes, if something is going to break it will break regardless of whether or not you are a licensed Corona dev, unfortunately.

When you deleted your developer certificate and remade it did you try remaking or redownloading your provisioning profiles as well? If you didn’t they may have issues with the new certificate so please let me know.

@Andriy - Was the update of Application loader so it would work with an update of Xcode to 4.3? Or did you update Application loader but NOT Xcode? [import]uid: 52491 topic_id: 22661 reply_id: 93492[/import]

#31

>>>When you deleted your developer certificate and remade it did you try remaking or redownloading your provisioning profiles as well?<<<

Yes, remade provisioning profile. They are marked as ‘invalid’ when you revoke certificate. So I remade them. [import]uid: 120570 topic_id: 22661 reply_id: 93495[/import]

#32

I encountered the same issue today–same error message after building using my dev cert. I submitted my app to Apple more than a week ago and everything was working fine. I didn’t change anything in my setup–XCode, Corona build, etc.

I’m using the ff.

XCode 4.2
Corona build 732
OSX 10.7.3

Any idea what happened? [import]uid: 44127 topic_id: 22661 reply_id: 93642[/import]

#33

Try updating the Xcode for 4.3.1
[import]uid: 89165 topic_id: 22661 reply_id: 93644[/import]

#34

@RSCDev: I’ve been meaning to do that, I guess now’s a good time. Did that fix the issue on your end?

Btw, how do you seamlessly upgrade to the latest version of XCode w/out affecting Corona? Do I have to uninstall Corona first, uninstall XCode, install new XCode then reinstall Corona SDK? [import]uid: 44127 topic_id: 22661 reply_id: 93645[/import]

#35

@egarayblas, do not panic! :slight_smile:
So, the first thing is that I did not have this “exactly” problem you and other guys are having - I mean getting that sinister message about codesign verification.

BUT by the other side, yes, I did have many problems regarding the update of my Xcode for the latest one, principally because I`ve had to renew my Apple Developer membership and so I needed to renew my certificates, provisionings profiles, and so on.

So after I get to renew my membership at all, I went to the mission of upgrade Xcode! Sincerely, by this time, (that all Ansca Staff worked on getting the Corona daily-builds working nice with the latest version of Xcode 4.3.1) it was not a pain! Opposite of it. I went to my Apple Developer Portal, clicked on iOS and found the link saying to upgrade the Xcode SDK. So this link went to Apple Store and direct for the Xcode latest version page. So I clicked INSTALL, it took a long time to download everything (1.6Gb) but after that it did install alone.

And then I made sure that my “old” Xcode was not in my Dock (the icon) and went to my applications folder (because the new Xcode installs itself there and not at the Developers folder anymore) and clicked on the Xcode icon there. After that it starts to install and ask you if you would like it to REMOVE your “older” version of Xcode (eg. 4.2.1), I said YES and it did all the job for me in a short time and so I was able already to open my new Xcode and its Organizer and see that everything was working (including my registered test devices, certificates and profiles).
So, after that I installed the latest daily-build of Corona (exactly the build 766) and went to try to BUILD for iOS. And so I went ahead and saw that CoronaSDK was beautifully “seeing” the new Xcode path and so it was able to build again! :slight_smile:
To summarize: Get the new Xcode at Apple Store, let your older version there where it is right now (just remove the Xcode of the Dock if you keep it there), after the download/installation complete, you click on Xcode and it will get installed seamlessly and even remove your (now) older version of it. Just make sure to have the latests CoronaSDK daily builds and I believe you would be good to keep going.

I hope that helps,

Rodrigo. [import]uid: 89165 topic_id: 22661 reply_id: 93652[/import]

#36

@Rodrigo: Thanks for the tips! I am downloading XCode 4.3.1 now and will also upgrade to the latest daily build after. I will report back if this fixes the “code signing” issue. [import]uid: 44127 topic_id: 22661 reply_id: 93655[/import]

#37

@egarayblas: You Welcome! :slight_smile: [import]uid: 89165 topic_id: 22661 reply_id: 93664[/import]

#38

I’d like to update this to say that on the download page we have updated 704 to support Xcode 4.3, so even if you are a trial user this is now an option for you - one worth trying at this stage, too.

Can you let me know results, please?

Thanks for posting this, Rodrigo :slight_smile: [import]uid: 52491 topic_id: 22661 reply_id: 93671[/import]

#39

@Peach, no problem, you know that Mrs! :slight_smile:
By the way thank YOU for letting us know that the beautiful Ansca team (hey @ewing :wink: ) got to support the latest stable build (704) THAT SUPPORTS older iOS versions 4.3- and still the latest Xcode 4.3.1 !

WOW! Great News!
Cheers,
Rodrigo. [import]uid: 89165 topic_id: 22661 reply_id: 93688[/import]

#40

Yes, it’s definitely awesome news - Eric (ewing) worked very hard on it, I think that guy deserves a holiday! [import]uid: 52491 topic_id: 22661 reply_id: 93730[/import]