codesign_wrapper-4.1: using Apple CA for profile evaluation error

_RSCdev · August 7, 2012, 1:07am

Here we go:

- Please post all the Terminal output you get for the bad build.

[code]Copyright © 2009-2012 C o r o n a L a b s I n c .
Version: 2.0.0
Build: 2012.870

Copyright © 2009-2012 C o r o n a L a b s I n c .
Version: 2.0.0
Build: 2012.870
The file sandbox for this project is located at the following folder:
(/Users/rscdev/Library/Application Support/Corona Simulator/HelloWorld-F8E2C5BA4CE84C12437755BD91CD8FA0)
Using Custom Build Id 998938d53cae4c47b8760cc764eea111
Using additional build settings from: /Applications/CoronaSDK/SampleCode/GettingStarted/HelloWorld/build.settings
Created XCENT: /var/folders/4x/00n54yln6d55x_0x6ygbs0s40000gn/T/1344325259/entitlements.xcent
Compressing/copying PNG /Applications/CoronaSDK/SampleCode/GettingStarted/HelloWorld/Icon-72.png to /Users/rscdev/Desktop/HelloWorld.app/Icon-72.png
Compressing/copying PNG /Applications/CoronaSDK/SampleCode/GettingStarted/HelloWorld/Icon-hdpi.png to /Users/rscdev/Desktop/HelloWorld.app/Icon-hdpi.png
Compressing/copying PNG /Applications/CoronaSDK/SampleCode/GettingStarted/HelloWorld/Icon-ldpi.png to /Users/rscdev/Desktop/HelloWorld.app/Icon-ldpi.png
Compressing/copying PNG /Applications/CoronaSDK/SampleCode/GettingStarted/HelloWorld/Icon-mdpi.png to /Users/rscdev/Desktop/HelloWorld.app/Icon-mdpi.png
Compressing/copying PNG /Applications/CoronaSDK/SampleCode/GettingStarted/HelloWorld/Icon.png to /Users/rscdev/Desktop/HelloWorld.app/Icon.png
Compressing/copying PNG /Applications/CoronaSDK/SampleCode/GettingStarted/HelloWorld/Icon@2x.png to /Users/rscdev/Desktop/HelloWorld.app/Icon@2x.png
Copying /Applications/CoronaSDK/SampleCode/GettingStarted/HelloWorld/world.jpg to /Users/rscdev/Desktop/HelloWorld.app/world.jpg
/Applications/CoronaSDK/SampleCode/GettingStarted/HelloWorld/world.jpg -> /Users/rscdev/Desktop/HelloWorld.app/world.jpg
/Users/rscdev/Desktop/HelloWorld.app: replacing existing signature
/Users/rscdev/Desktop/HelloWorld.app: signed bundle with Mach-O thin (armv7) [HelloWorld]
2012-08-07 04:41:12.466 Corona Simulator[15559:707] validationTool: /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/Validation[/code]
- Is blank in the /Users/ /Desktop/Fishies… something you blanked out or is it actually blank like that?

I`ve blanked that out.
- Would you post a screenshot or submit a bug report or email to Peach and/or me of your Keychain so we can see if there is anything suspicious. I want to see the My Certificates, Keys, and Certificates sections.

Ive done it right now and sent for Peach already a mail with 2 attacheds file (the HelloWorld built and also 6 screenshots of all sections you asked above). I sent only for @Peach because I do not have your personal mail.
- Would you also zip up and send us a built binary that doesn’t work? Please build the GettingStarted/HelloWorld program.

The same as above.
- Would you try doing a native Xcode build? Start a new OpenGL ES template and get it to build and run on your device.

I`ve done it following your guidance right now and I was able to build for my iPhone 4 as well as only run the iOS Simulator. [import]uid: 89165 topic_id: 29156 reply_id: 118608[/import]

peach_pellen · August 7, 2012, 5:33am

Will forward your email to Eric so he has it as well; I’ll be taking a look myself although honestly this whole thing is pretty confusing at this stage. [import]uid: 52491 topic_id: 29156 reply_id: 118653[/import]

_RSCdev · August 7, 2012, 9:39am

@Peach ,

Thank you very much.

I really want to see that we get to solve this.
Let me know how it goes as well please.
Cheers,
Rodrigo. [import]uid: 89165 topic_id: 29156 reply_id: 118704[/import]

ewing · August 7, 2012, 3:46pm

By the way, did you actually try to install the binary onto a device despite the error? Does it install and work?
[import]uid: 7563 topic_id: 29156 reply_id: 118764[/import]

Tom · August 7, 2012, 4:06pm

We ran the validation tool on the HelloWorld.app file from Rodrigo and it didn’t produce any error message on our 10.8 machine running Xcode 4.4. Rodrigo also said that the app does install and run on a device (despite the build error message.)

If you are seeing this message can you run the following from the command line (Terminal) and let us know the results. Also, try installing the app on a device to see if it runs. Please build with your Developer certificate.

/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/Validation /path/to/HelloWorld.app

(You will need to change the “/path/to/…” to point to your own app file.)

We recommend trying this on the HelloWorld sample app to eliminate any project differences that could cause build errors.

Thanks,
Tom [import]uid: 7559 topic_id: 29156 reply_id: 118768[/import]

_RSCdev · August 7, 2012, 4:58pm

@Eric,

Yes. It does install and work (despite the error) as I`ve said you in the mail.
Thanks,
Rodrigo. [import]uid: 89165 topic_id: 29156 reply_id: 118773[/import]

_RSCdev · August 7, 2012, 5:02pm

@Tom,

A little bit more info for you is that I`ve upgraded my Xcode 4.4 today for the latest available at Mac AppStore that is the 4.4.1 and also installed the Command Line tool but no way! The same error message comes up always when building with the Developer Profile (*Team Provisioning Profile).

So even the Xcode upgraded did not change the error message on builds at all.
Rodrigo. [import]uid: 89165 topic_id: 29156 reply_id: 118774[/import]

Tom · August 7, 2012, 5:16pm

@Rodrigo,

Can you open a Terminal window and run the Validation tool manually to see if it gives you the same error message?
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/Validation /path/to/HelloWorld.app

(You will need to change the “/path/to/…” to point to your own app file.)
[import]uid: 7559 topic_id: 29156 reply_id: 118780[/import]

_RSCdev · August 7, 2012, 5:54pm

@Tom,

Ive done just this as following yours and @Erics advice/request. (also responded to the mail).

I got the below results from command line:

  
RSCdev-MacBook-Pro:~ rscdev$ /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/Validation /Users/rscdev/Desktop/HelloWorld.app  
  
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/rscdev/Desktop/HelloWorld.app/HelloWorld  
codesign\_wrapper-4.1: using Apple CA for profile evaluation  
/Users/rscdev/Desktop/HelloWorld.app: valid on disk  
/Users/rscdev/Desktop/HelloWorld.app: satisfies its Designated Requirement  
test-requirement: code failed to satisfy specified code requirement(s)  
codesign\_wrapper-4.1: failed to execute codesign(1)  
 - (null)

Thanks,
Rodrigo
[import]uid: 89165 topic_id: 29156 reply_id: 118783[/import]

jamiewilburn · August 8, 2012, 1:10pm

I just wanted to chime in. I have an app that is currently on the B&N Nook store. It was built using the latest public release of Corona. Everything went fine. We spent another couple of months working on version 1.1 which I’m now trying to release to all 3 platforms.

As of an hour ago I was able to build the newest version of my apps with no problems. I’m running an older MacBook with Mountain Lion, and the latest version of XCode (4.4) as installed (Updated) from the App Store.

Within the last hour I filled out the iTunes Connect application forms, and got the app ready to submit. When I loaded Application Launcher, it would not let me click on the file I built with Corona. It was grayed out. I deleted the file, went to create a new build, and got the codesign-wrapper 4-1 error as mentioned above. This was the first time I’ve seen it, and the only thing that has changed between now and an hour ago when I was able to build the same file just fine is that I executed Application Launcher.

I’m running the Corona SDK Daily Build 2012.870.

I admit to being a novice to this whole thing and it’s very likely I’m doing something wrong, but I wanted to pass along my experiences in case there’s anything in there that helps the developers. I’ll spend tomorrow trying to resolve this issue further running through the tips suggested above and report back my findings. [import]uid: 98297 topic_id: 29156 reply_id: 118933[/import]

Tom · August 8, 2012, 1:24pm

@jamiewilburn,

The code design-wrapper error was occurring when building with a Developer provisioning file and not the Distribution provisioning file. If you building for Developer, the upload button will be grayed out in iTunes Connect. You will also find that there is no .zip file for your project either.

-Tom [import]uid: 7559 topic_id: 29156 reply_id: 118938[/import]

jamiewilburn · August 8, 2012, 1:45pm

Oh man, thank you so much for that. I created that dev certificate back in Dec when we first started toying with Corona and this is the first time I’ve actually launched anything on the App Store. I had completely forgotten about the Dev and Distribution certificates being separate.

Got the new certificate, just pushed the app up to the server, everything seems to have gone fine. I’ll let you know in when it gets accepted. [import]uid: 98297 topic_id: 29156 reply_id: 118944[/import]

_RSCdev · August 8, 2012, 7:16pm

So @Tom following up what is going on here about this “terrible weird warning message” is that @jamiewilburn is getting the same and exact warning as some of us and his shared info lead us to that it is due to the “Developer profile” only.

PS: As I said in the mail, I think that as more Corona Devs get to build using their “Developer profiles” so more people well see here telling about this. The things are that the majority use their AdHoc ones and so theyll not see any weird warning IMO.
Thanks,
Rodrigo. [import]uid: 89165 topic_id: 29156 reply_id: 118983[/import]

ewing · August 8, 2012, 7:48pm

Okay based on a bunch of experiments with Rodrigo (thanks for the help), we’re going to write this off as an Apple bug.

We’re going to make our validation process ignore this message so you guys aren’t bothered by this message. Please try the next daily build (786) when it becomes available. Let us know if it clears up that warning.

I recommend you file a bug with Apple about this Apple CA error thing for those of you hitting it. In your report, emphasize that:

you want to run to the tool while developing (Debug) so you know the problems earlier. (This is why we started running it almost 2 years ago.)
only some people seem to get that error
Show them how to run the command line tool and attach both your binary and paste your output which includes the Apple CA error:
e.g.

/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/Validation /Users/rscdev/Desktop/HelloWorld.app  
  
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/rscdev/Desktop/HelloWorld.app/HelloWorld  
codesign\_wrapper-4.1: using Apple CA for profile evaluation  
/Users/rscdev/Desktop/HelloWorld.app: valid on disk  
/Users/rscdev/Desktop/HelloWorld.app: satisfies its Designated Requirement  
test-requirement: code failed to satisfy specified code requirement(s)  
codesign\_wrapper-4.1: failed to execute codesign(1)  
 - (null)

[import]uid: 7563 topic_id: 29156 reply_id: 118986[/import]

_RSCdev · August 8, 2012, 8:11pm

@Eric, @Tom and Team,

I thank you all too.

Yes, we`ve done a lot of tests and am going to file a bug with Apple about all this.

After that I`ll let you know my bug report number for you to mention it as well.

EDIT: Well, I did that. So here am pasting my Apple Bug report ID for you @Eric, @Tom, and also for other developers that are getting the same problem if want to mention mine already when submitting a bug there.

My tracking number for this issue is Bug ID# 12062750

Cheers,
Rodrigo. [import]uid: 89165 topic_id: 29156 reply_id: 118988[/import]

_RSCdev · August 9, 2012, 2:11pm

@Eric, @Tom, @Peach and all the CoronaLabs Team ,

I`ve tested out right now the daily-build number 876 and you Team rock! YES! You got the weird warning message to be out of my(our) vision! Even knowing that its “behind” the scene my mind feel better of not seeing these disturbing unexpected and inexplicable bugs.

PS: By now I`ll only have to wait to see if Apple will reply something about my bug report with them and I really hope so. Fingers crossed!
Thank you all Team!

Cheers,
Rodrigo. [import]uid: 89165 topic_id: 29156 reply_id: 119146[/import]

Nevistech · September 17, 2012, 12:13pm

Hiya,

Was this problem solved? (other than using the latest corona build to ignore the problem) I am getting exactly the same error message “… using Apple CA for profile evaluation”.
It started on exactly the same day that I built and uploaded my first app to the App Store.

During this process I did the following:

upgraded my MAC OS to 10.7.4
upgraded XCode to 4.4.1
(above 2 steps were needed to get the latest Application Loader
changed some of my provisioning profiles around so that everything was aligned (i.e. the correct
Distribution profile was used, aligned to the App ID etc)
uploaded to the App Store
breathed a sigh of relief and opened the Champagne!
carried on developing using the developer profile
suddenly the error occurred

Any of the above things could be related to the bug.

Really annoyingly, now any builds I do seem to have the same underlying filename. So even if I call the app something different, it will not install until I delete the old version of the app from the phone.
I have a feeling these two issues are related.

I’ve just tried re-building some old app versions (which used to build perfectly) and exactly the same errors occur, which rules out config issues, at least in terms of the lua code

cheers,
Anthony

[import]uid: 87194 topic_id: 29156 reply_id: 124215[/import]

Nevistech · September 17, 2012, 12:13pm