certificate errors after Xcode 4.2 upgrade (Build 4D199)

Solar2D General Questions/Discussion
#1

Hello all.

I’ve upgraded the Xcode to the latest version in order to test my apps for iOS 5. Somewhere in the process my certificates got screwed up so I had to clean house, and redo the certificates from scratch. Everything looks and works fine now in Xcode (including building debug and distribution builds and submitting to Apple), but Corona SDK is another beast.

this is what I get when I build (any) applications with Corona SDK:

“warning: Application failed codesign verification. The signature was invalid, or it was not signed with an iPhone Distribution Certificate. (-19011)
Executable=/Users/user/Desktop/Test.app/Test
codesign_wrapper-0.7.10: using Apple CA for profile evaluation”

I checked and rechecked everything that I knew of, but I just can’t get this error to go away.

anyone please ?

thank you! [import]uid: 39057 topic_id: 16046 reply_id: 316046[/import]

#2

Which build of Corona SDK are you using? [import]uid: 48203 topic_id: 16046 reply_id: 59627[/import]

#3

2011.591 on Mac OS 10.7.1

I haven’t had any problems with Certificates until a couple of days ago. That’s when I installed the latest Xcode 4.2 with iOS5 GM SDK. [import]uid: 39057 topic_id: 16046 reply_id: 59630[/import]

#4

I ended up reinstalling Mac OS 10.7.1 from scratch as I did not see any other solution (and already wasted hours trying to find one).
All is well now.

One thing I noticed is that the first time I tried to build with Corona SDK, the system asked me whether I was allowing access to my keychain in order for Corona SDK to access the certificates.
I did not get such question after I changed my certificates on my old system. Might have had something to do with the errors, I would think.

cheers [import]uid: 39057 topic_id: 16046 reply_id: 59741[/import]

#5

Can someone from Corona please answer on this one, I have the same issue with the latest daily build just after upgrading XCODE for iOS5 support and I can’t make it go away and I do not want to reinstall the whole computer. [import]uid: 22737 topic_id: 16046 reply_id: 81657[/import]

#6

Your signing with a Development Certificate right?
No need to worry. Nothing has gone wrong. This is just a warning that you haven’t signed with a Distribution certificate, and means you can’t use this build to upload to iTunes Connect for AppStore approval.
You can still use this build to transfer to your development devices for testing.

Once you sign with a Distribution certificate this message will not appear.

[import]uid: 70847 topic_id: 16046 reply_id: 81658[/import]

#7

Hey
I can’t upload apps no longer to TestflightApp due to this warning so how is it a no worry issue? [import]uid: 22737 topic_id: 16046 reply_id: 81659[/import]

#8

Well, I can’t speak for Testflightapp, as I’ve never used that service.

I get the same warning message every time when I sign with a Development certificate, and I have no problems installing the apps on real devices…
[import]uid: 70847 topic_id: 16046 reply_id: 81660[/import]

#9

I just solved the problem!

It has nothing to do with Corona per se. This is an issue with TestflightApp’s validation of Apple’s certificates.
I have never used this service so I created an account (since it’s free :slight_smile: ), and tested an upload.
I got an error message, but there was info about this error on their website.

This whole issue happens because you have iCloud enabled in your AppID. You will need to go to Apple’s Provisioning Portal and deactivate iCloud for your AppID, and then regenerate all your provisioning profiles for the app.
Recompile your app with Corona and your new Provisioning Profile and you’ll be able to upload your app to TestflightApp.

Since Corona doesn’t support iCloud yet, your AppID shouldn’t either. Normally it doesn’t matter, but TestflightApp performs validations between binary and profile that make it matter.

NOTICE:
You’ll still get the warning message you’ve seen before if you compile with a Development Certificate though.

In my opinion you shouldn’t distribute apps with a Development Certificate to beta testers.
You should create an AdHoc Distribution profile and compile with that when you plan to upload to TestflightApp. This way you will *not* see the warning message since it’s a valid Distribution Profile.

Hope this helps…
[import]uid: 70847 topic_id: 16046 reply_id: 81670[/import]