error message popup when first time to use xcode 4.5.2 with build 971

Solar2D Daily Builds and Public Releases
#22

I’m glad you found the problem. Setting that option in Xcode Preferences has never come up before because it’s always been set correctly. Something must of happened when you upgraded Xcode. Are you sure you don’t have multiple copies of Xcode installed on your system?

Corona uses Xcode’s tools during the build process and the locations of those tools sometimes changes with new versions of Xcode. If the location was wrong you would see build errors even before the signing occurred. The fact that you received a signing error, indicates that it was using an older signing tool. I believe setting the Location option forced it to use Xcode’s 4.5.2 tools instead. Maybe the previous copy of Xcode was not completely removed from your system and Corona was using those tools instead of the latest Xcode installed.
[import]uid: 7559 topic_id: 33485 reply_id: 134849[/import]

#23

The ghost of xcode’s past, lol, come to haunt me.

I deleted xcode completely from my system before installing the new xcode for the second time, but maybe there was something that was left over … super strange.

Hopefully it’ll help anyone else who might be having issues like that.

Thanks for all the help :slight_smile:

K [import]uid: 142918 topic_id: 33485 reply_id: 134858[/import]

#24

I’m having this issue as well.

I’ve previously published two apps (through xCode) and am a few weeks away from releasing my first game using Corona. I’ve been using Corona since May and have not had any issues until I upgraded to 971 (to work with iPhone 5).

I’ve uninstalled all provisions, reinstalled, checked for multiple certs, restarted xcode, restarted computer to no avail.

Here’s the error I’m receiving:

warning: Application failed codesign verification. The signature was invalid, contains disallowed entitlements, or it was not signed with an iPhone Distribution Certificate. (-19011)
failed to extract requirements data: 1
/Users/kurtbieg/Desktop/MyGame.app: invalid signature (code or signature have been modified)
failed to extract entitlements: 1
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 MyGame is a valid Mach executable that’s properly codesigned. (-19050)
/Users/kurtbieg/Desktop/MyGame.app/MyGame: invalid signature (code or signature have been modified)

  • (null)

Hopefully someone can help out, super frustrating.

K [import]uid: 142918 topic_id: 33485 reply_id: 134700[/import]

#25

Do you get the error if you build one of Corona’s sample apps? If you don’t than something in your project file is causing the problem. Try removing the build.settings file to see if the error goes away.

If you go back to another previous build, do you still get the error?
[import]uid: 7559 topic_id: 33485 reply_id: 134704[/import]

#26

If I go back to the last stable build of Corona it goes away, 894.

Also, removed build and config, still gettin it.

Tried a Corona example, same error.

It’s like it isn’t refreshing the location of the certificate, I checked the MobileDevices/Provision Profiles folder, it’s all there.

Any other ideas, I really need to get back to working on this game :frowning:

K [import]uid: 142918 topic_id: 33485 reply_id: 134707[/import]

#27

I think this is beyond Corona and a basic configuration problem. I bet if you tried to build a simple Xcode project you would have the same signing issue. You could prove this by building and signing a Xcode project and see if you get the same error.

Did you try Refreshing Xcode (click on the Provisioning Profiles tab and click Refresh).
The other thing I would suggest is removing and reinstalling Xcode.

In the past one user had to contact Apple to help resolve this type of issue. [import]uid: 7559 topic_id: 33485 reply_id: 134714[/import]

#28

kurtbeig - I was experiencing the same problem this morning and apparently just fixed it. I was running XCode 4.5 and Corona build 2012.840, but switched to 2012.971 this morning. As soon as I tried to build for device, I got this error (same as yours):

failed to extract requirements data: 1
/Users/Nate/Desktop/MyGame.app: invalid signature (code or signature have been modified)
failed to extract entitlements: 1
AssertMacros: entitlements_requested, At least need an application-identifier entitlements file: codesign_wrapper.c, line: 879

  • (null)

When I switched back to 2012.840, the error went away. When I switched back to 2012.971, the error came back. I then created a new provisioning profile, but still no luck. Then I just upgraded XCode to 4.5.2. Now, the error is gone and I can build for device fine (running on iPad 2 with no problems).

Obviously, you already have 4.5.2. But if I were you, I’d delete and re-install XCode and see what happens. Hopefully, that will do the trick. [import]uid: 135391 topic_id: 33485 reply_id: 134719[/import]

#29

Ok, deleted xcode and reinstalling.

Fingers crossed!

I’ll let you know if that does it.

Thanks!

K [import]uid: 142918 topic_id: 33485 reply_id: 134722[/import]

#30

Didn’t work :frowning:

I deleted and reinstalled xCode.

I then, just for kicks, created a brand new development provision profile.

Works in the newly installed xCode but I am still getting the same error in Corona.

Any other ideas? Nate, was there something you did particularly that might work for me? Did you delete Corona before installing, did you delete directories or something?

I submitted a request for tech support from Apple, but seeing as it’s not a problem on their end I’m expecting someone from Corona can help me get back up and running.

K [import]uid: 142918 topic_id: 33485 reply_id: 134728[/import]

#31

Yes, I also did completely delete Corona and re-install, but I did that before I updated xCode and it didn’t work until I updated xCode. Very strange.

Does anyone else from Corona remember seeing this issue come up on the forums recently? Seems unlikely that we’re the only two that have experienced it. [import]uid: 135391 topic_id: 33485 reply_id: 134731[/import]

#32

I just went back to Corona build 894, and it builds out without an issue.

So I can build from there and from xCode, to me that says it’s an issue with the Corona build.

Some thing having to do with connecting to the application loader?

K [import]uid: 142918 topic_id: 33485 reply_id: 134735[/import]

#33

We have no other reports of build problems and we can’t debug configuration errors like this since we can’t reproduce the problem. If you are running the most recent Xcode and CoronaSDK and you don’t have problems with expired certs or provisioning files, I don’t know what else to tell you except to verify it again.

When you look the the Provisioning Profiles in Xcode, does everything show green (Valid Profile)?

When you do a Xcode build, did you do a signed developer build using the same provisioning profile you used in Corona? Try doing an AdHoc Xcode build too. I’m not sure if the Xcode Developer build verifies the signed app or not so you may be getting an error if you force it to validate the build. I believe we force a validation on all Corona builds. (Apple’s validation tool is the one giving you the signing error.)

Have you tried installing the failed Corona build on an actual device to see if it loads and runs? That would tell you if it’s a false error or not. [import]uid: 7559 topic_id: 33485 reply_id: 134737[/import]

#34

Tom - when I was getting the error, the builds would not load onto a device. xCode gave me a “The application does not have a valid signature.” error. [import]uid: 135391 topic_id: 33485 reply_id: 134761[/import]

#35

Hi Tom,

I tried all of your recommendations. Nothing is working though.

All profiles are green, no expired duplicates, tried development and adhoc provisions but both fail on the most recent corona build. If I roll back to the last public corona release they build out just fine.

I tried putting the game on the phone, disregarding the error, but like Nate said, it refuses stating it hasn’t been signed correctly.

I’ve been doing this for a while, and if its not working on the most recent build but works in Xcode and the previous build then there is something that isn’t connecting correctly in the recent release. Is there someone I can discuss this with offline, I’m submitting this game in about 3 weeks, and need to be able to format for iPhone 5.

K [import]uid: 142918 topic_id: 33485 reply_id: 134763[/import]

#36

The difference between building for 894 and 971 is 894 builds for iOS 5.0 and the recent builds are for iOS 6.0.

Do you have multiple copies of Xcode on your machine? It could be that Corona is not picking Xcode 4.5.2, which is causing a problem. Building for iOS 6 with an older Xcode can errors like this.

If you only have one Xcode on your machine and it’s the most recent one, the final test I would have you do is an Xcode build of an Xcode project and try to install it on your iPhone or iPad using the same provisioning file that is failing with Corona. [import]uid: 7559 topic_id: 33485 reply_id: 134773[/import]

#37

ZOMFG I got it!

I went into xCode, rooted around through the preferences and noticed that on the last menu “Locations” there is an option for “Command line tools” which was blank. I clicked on it and there was an option for xCode 4.5.2, after I selected it I had to restart the Corona simulator. After that, built out just dandy!

Yay!

K [import]uid: 142918 topic_id: 33485 reply_id: 134831[/import]

#38

Although I am experiencing noticable lag with the upgraded build which was not present previously. Is this a known issue?

K [import]uid: 142918 topic_id: 33485 reply_id: 134835[/import]

#39

Nevermind, test config file I was using while trying to fix all this was missing fps.

K [import]uid: 142918 topic_id: 33485 reply_id: 134838[/import]

#40

I’m glad you found the problem. Setting that option in Xcode Preferences has never come up before because it’s always been set correctly. Something must of happened when you upgraded Xcode. Are you sure you don’t have multiple copies of Xcode installed on your system?

Corona uses Xcode’s tools during the build process and the locations of those tools sometimes changes with new versions of Xcode. If the location was wrong you would see build errors even before the signing occurred. The fact that you received a signing error, indicates that it was using an older signing tool. I believe setting the Location option forced it to use Xcode’s 4.5.2 tools instead. Maybe the previous copy of Xcode was not completely removed from your system and Corona was using those tools instead of the latest Xcode installed.
[import]uid: 7559 topic_id: 33485 reply_id: 134849[/import]

#41

The ghost of xcode’s past, lol, come to haunt me.

I deleted xcode completely from my system before installing the new xcode for the second time, but maybe there was something that was left over … super strange.

Hopefully it’ll help anyone else who might be having issues like that.

Thanks for all the help :slight_smile:

K [import]uid: 142918 topic_id: 33485 reply_id: 134858[/import]