codesign_wrapper-4.1: using Apple CA for profile evaluation error

Getting Started Newbie Questions
#1

When I try to do a developer build I get this error “codesign_wrapper-4.1: using Apple CA for profile evaluation” and I don’t have the error when I try to do a distribution build. Anyone have any clues why this is happening? Never happened before today.
[import]uid: 79620 topic_id: 29156 reply_id: 329156[/import]

#2

Sounds like a possible matching issue with identifiers; http://stackoverflow.com/questions/11489097/application-failed-code-sign-verification-log-interpretation [import]uid: 52491 topic_id: 29156 reply_id: 117271[/import]

#3

Yeah I read that post and it made absolutely no sense to me. No idea how to fix this :frowning: [import]uid: 79620 topic_id: 29156 reply_id: 117319[/import]

#4

Well, right now I would think there may be something in your build.settings that is causing the problem, potentially - could you post those, please? [import]uid: 52491 topic_id: 29156 reply_id: 117383[/import]

#5

[code]
settings =
{
orientation =
{
default = “landscapeRight”,
supported = { “landscapeRight”, “landscapeLeft” },
},

iphone =
{
plist =
{
UIStatusBarHidden=true,
UIPrerenderedIcon = true,
UIApplicationExitsOnSuspend = true,
CFBundleIconFile = “Icon.png”,
CFBundleIconFiles = {
“Icon.png”,
“Icon@2x.png”,
“Icon-72.png”,
},
},
}
}
[/code] [import]uid: 79620 topic_id: 29156 reply_id: 117427[/import]

#6

Hmmm, nothing there looks to be a problem. Have you attempted building other apps with development profiles and had success, or are they all having issues with dev rather than dist? [import]uid: 52491 topic_id: 29156 reply_id: 117525[/import]

#7

I’ve actually revoked and created new profiles… it’s all the same. I’m guessing Corona taps into Xcode to verify code signing and I’m wondering if it’s something to do with Xcode. Maybe there’s a way to clear all prefs in Xcode and start clean. I also tried deleting Xcode and re-downloading it but I know that when you trash a program it usually keeps the prefs hidden on your computer and reloads them if/when you install that program again.

I tried some of the sample projects that come with Corona too. No luck :frowning: [import]uid: 79620 topic_id: 29156 reply_id: 117529[/import]

#8

Very strange - I’m not totally sure what to advise at this point. I’m going to see if anyone else on the team has encountered this.

In the meantime, to clarify, this happens with multiple development profiles, yes? [import]uid: 52491 topic_id: 29156 reply_id: 117680[/import]

#9

I’m also having this ‘error’ pop up when i build dev builds. Doesn’t seem to affect anything as the app runs fine on my devices. And i also don’t get the error pop up when building distribution.
I do recall that its a similar error pop up that occurred in corona builds from some time ago.
My build.settings is as follows (note some names replaced with xxxx on purpose and all work fine). All i can think of is i just renewed my apple dev license (and also my corona license). Could it be due to that?

[lua]settings =
{

iphone =
{

plist =
{
UIApplicationExitsOnSuspend = false,
CFBundleURLTypes =
{
{
CFBundleURLSchemes =
{
“fbxxxxxxxxxx”,
}
}
},
UIPrerenderedIcon = true,
UIStatusBarHidden = true,
MinimumOSRequirement = “4.3.0”,
CFBundleIconFile = “Icon.png”,
CFBundleIconFiles = {
“Icon.png”,
“Icon@2x.png”,
“Icon-72.png”,
“Icon-72@2x.png”,
“Icon-Small-50.png”,
“Icon-Small-50@2x.png”,
“Icon-Small.png”,
“Icon-Small@2x.png”
},
CFBundleIdentifier = “com.vdvgames.xxxx”,
CFBundleDisplayName = “xxxx”,
UIAppFonts =
{
“xxxx.ttf”
}
},
components = {}
},
orientation =
{
default = “portrait”,
supported =
{
“portrait”,
},
},
}[/lua] [import]uid: 66228 topic_id: 29156 reply_id: 117965[/import]

#10

Same problem here. I was already tearing my hair out because I thought it was yet another issue with these damn certificates.

Here’s part of my build.settings. Worked before, not changed, and even have app in Appstore with these settings… (Appstore version has been built w/SDK 840 and OSX10.8/XCode 4.4 as well, no problems then)

Currently using build 868, maybe there’s something wrong there? (and like above, distribution build works OK, only the dev’t build gives this message - did not try ad hoc build btw)

[code]

settings =
{
orientation =
{
default =“portrait”,
content = “portrait”,
supported =
{
“portrait”
},
},

iphone =
{
plist =
{
UIApplicationExitsOnSuspend = true,
UIInterfaceOrientation = “UIInterfaceOrientationPortrait”,
UILaunchImageFile = “galious_splash.png”,
UIStatusBarHidden = true,
UIStatusBarStyle = “UIStatusBarStyleDefault”,
CFBundleIdentifier = “com.galious.solarpvcalculator”,
CFBundleDisplayName = “SolarPVCalc”,
CFBundleIconFile = “Icon.png”,
CFBundleIconFiles =
{
“Icon.png”,
“Icon@2x.png”,
“Icon-72.png”,
},
CFBundleLocalizations =
{
“en”,
“nl”,
“de”,
“fr”,
“it”,
“es”
},
},
[/code] [import]uid: 106658 topic_id: 29156 reply_id: 117980[/import]

#11

Wow… sorry to hear you guys are having the same issue but i’m happy I’m not the only one. I haven’t had luck tracking it down yet but I tried a few things. I ran disk utility last night and it found a few permissions that were messed up so I fixed them… still no luck though. I can’t quite remember but I though there was an update for xcode recently… like in the last couple of weeks. I think this problem started right after I did the update so it’s my thinking that it’s an xcode issue. [import]uid: 79620 topic_id: 29156 reply_id: 118024[/import]

#12

Hey guys;

Asked a colleague (the genius, Eric Wing) what he thought about this-

_Some guesses:

  • Do the sample projects build? Maybe they picked funny names for their own projects which is creating a funny bundle identifier but their distribution ticket has a full bundle identifier.
  • Make sure xcode-select is pointing to the correct version/location of Xcode 4.4.
  • If they still have Xcode 4.3 on a 10.8 system, they should delete it. (It won’t work on 10.8 anyway.)
  • Install or Update the Command Line Tools for Xcode (see screenshot, though mine is outdated on a 10.7 system). We don’t require these to be installed, but maybe the user installed them before and a stale version is being invoked by our process._

Could you all take a look at these things and get back to me, please?

Peach :slight_smile: [import]uid: 52491 topic_id: 29156 reply_id: 118301[/import]

#13

Hi Peach,

for me its a ‘nope’ to the above bundle ids issues or Xcode. The only thing for me i could think of and perhaps you could confirm is this could be the issue is that I just renewed my corona license (i doubt this has any bearing) and I just renewed my apple dev license (which means i had to recreate a new cert and go through the hassle of all that keychain stuff) and then of course create a new provisioning profile. However I only created a new dev cert and dev prov. profile not a dist. cert and profile, so perhaps thats why there’s no weird error pop up when i build for distribution. Will confirm abt this in a day or so as i do now need to renew my dist. cert also… oh the hassle of keychain certs,keys, profiles…groan!

Perhaps the other could indicate whether they have also just renewed any certs or profiles?

BTW, i’m building using .849 (but again, didn’t have any weird error pop up until i renewed my apple dev. cert) [import]uid: 66228 topic_id: 29156 reply_id: 118306[/import]

#14

I was working on a project yesterday morning and I got up this morning and now I have this error, I think the only thing I did was upgrade to latest daily build, nothing else. [import]uid: 8697 topic_id: 29156 reply_id: 118365[/import]

#15

Hey devs,

I facing the same problem as well!

Always getting this sinister message when trying to build using a developer profile:

codesign_wrapper-4.1: using Apple CA for profile evaluation error
PS: @Peach : I`ve tested everything you said above and still got nothing changed about this error message when building with developer profile.

PS2: BTW, I`ve made a build 3 days ago using the same Corona version as now (868) and I did not see any error even when building with the developer profile and even using the OSX 10.8 with Xcode 4.4 already.

UPDATE : Ive completely removed/deleted the Xcode 4.4 (4F250) and re-downloaded it from Mac AppStore (the hard 1.56Gb size) and re-installed it so from zero and after that Ive checked into Terminal for the command xcode-select -print-path and it displayed that my Xcode path is /Applications/Xcode.app/Contents/Developer. So I think that it all is OK but I still get the exactly same ERROR message when building with developer profile. :frowning:

UPDATE 2 : FYI: the latest line ( and the one displayed just before the ERROR message window ) that is showed into my Terminal when building with the developer profile is it: 2012-08-05 10:56:10.716 Corona Simulator[4618:707] validationTool: /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/Validation

UPDATE 3: Here is the sinister ERROR message!

Does it help the Corona Team debug this thing?

I need help as well please.
Thanks in advance,
Rodrigo.
SO, what to do? :S

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

#16

AI’ve just upgraded, made keys, provision profiles, etc. I’m having similar problems as Jacques1 and RSCdev and haven’t heard any solutions. Building on the Android works fine.

***AssertMacros: entitlements_requested, At least need an application-identifier entitlements file: codesign_wrapper.c, line: 879

  • (null)

***warning: Unable to extract codesigning entitlements from your application. Please make sure beta is a valid Mach executable that’s properly codesigned. (-19050)

***/Desktop/beta.app/beta: invalid signature (code or signature have been modified)

  • (null) [import]uid: 114389 topic_id: 29156 reply_id: 118418[/import]
#17

Thank you for the additional info guys, I’m going to bring this up in the meeting this morning and see if we can get some insight. We’ve been struggling to reproduce the issue on our end thus far, some of this may prove very useful info. [import]uid: 52491 topic_id: 29156 reply_id: 118467[/import]

#18

This thread might be related:
http://developer.coronalabs.com/forum/2012/05/06/certificates-expired-ios

Would you guys verify you don’t have duplicate certificates in your Keychain.
If you still have problems and you’ve done all the things mentioned earlier in the thread, some other things to try:

  • Make sure to launch Xcode (the version pointed to by xcode-select) at least once. You must agree to Apple’s license agreement at least once otherwise Xcode may not work.
  • Make sure to launch the Application Loader at least once (same License reason)
  • Please tell us how you upgraded to 10.8.
    – Did you do a clean install, upgrade from 10.7, or upgrade from 10.6?
  • What are your system specs?

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

#19

@ewing ,

After try everything you said above and even more I got nothing anyway! I`m frustrated, really.

So, by part:

  1. Ive checked out the link you passed above and Ive deleted everything I would see “duplicated” or having any “red X” over it (anyway it was only one referencing iPhone Configuration Utility and so I deleted it anyway)

    • Make sure to launch Xcode (the version pointed to by xcode-select) at least once. You must agree to Apple’s license agreement at least once otherwise Xcode may not work.

Yes, as I said above as well, I`ve done this and I can see that my Xcode has the right path at all

    • Make sure to launch the Application Loader at least once (same License reason)

Yes, Ive done it as well as Ive uploaded my latest app for Apple 5 days ago without any error like this.

    • Please tell us how you upgraded to 10.8.
      – Did you do a clean install, upgrade from 10.7, or upgrade from 10.6?

I`ve upgraded my OSX from 10.7.3 to 10.8 downloading and installing it from Mac App Store.

    • What are your system specs?

MacBook Pro 13" (earlier 2011) , core i5 2.3Ghz, 8Gb RAM, OS X 10.8 (12A269)

I hope that helps and I`m looking forward a solution for this trouble my friends.
Thanks,
Rodrigo. [import]uid: 89165 topic_id: 29156 reply_id: 118588[/import]

#20
  • Please post all the Terminal output you get for the bad build.
  • Is blank in the /Users/ /Desktop/Fishies… something you blanked out or is it actually blank like that?
  • 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.
  • Would you also zip up and send us a built binary that doesn’t work? Please build the GettingStarted/HelloWorld program.
  • Would you try doing a native Xcode build? Start a new OpenGL ES template and get it to build and run on your device.
    [import]uid: 7563 topic_id: 29156 reply_id: 118603[/import]