Failed Codesign Verification

Solar2D General Questions/Discussion
#1

The codesign failure thing has recently happened to me. I’m researching what the next steps to take are.

Looking at the forums, there was quite a bit of activity on this subject last year and I’m wondering how people have got on since then.

So, if anyone is having the same problem, can relate what they did to fix it if its not already on the forum, or there seems to be a general concuss of what to do, it would be good to know. Thanks.
[import]uid: 94653 topic_id: 23232 reply_id: 323232[/import]

#2

There are a few things we suggest.

First is to ask; have you successfully built before or is this your first time?

Next is to try and build one of our sample apps, does it work?

If no, then you can be sure it is a certificate issue - often the fastest way to resolve this is to destory and recreate your certificates and redownload your provisioning profiles.

Peach :slight_smile: [import]uid: 52491 topic_id: 23232 reply_id: 92963[/import]

#3

This is my second build. One’s in the queue at Apple.

I’ve tried one of the sample apps and it works fine.

Yes it looks like a clean out is the way to go.

Couple of questions though: Do I include deleting the Apple Worldwide Developer Relations Certification Authority certificate?

The reason I ask is, I don’t want to take any actions that will effect the app I already have waiting for review.

In which case, is it also best to leave the dist/dev certificates in the keychain for that app alone. Just clean out the ones for the offending app in question? [import]uid: 94653 topic_id: 23232 reply_id: 92974[/import]

#4

Peach, re-reading your reply, when you say ‘try and build on of our sample apps,’ does that include, get an apple developer cert and test with it?

I’ve built the hello world app and run its main.lua file with the simulator. It worked fine but that was without getting a developer certificate. [import]uid: 94653 topic_id: 23232 reply_id: 92978[/import]

#5

Hey - Peach, I forgot to say thanks… x [import]uid: 94653 topic_id: 23232 reply_id: 92986[/import]

#6

I’m not sure that is the case but when using Testflightapp for sharing our builds with testers we came across some signing issues.

Basicaly what was causing them were hidden files in the project directory. Unless we removed all hidden files the signing process would fail. Well, actualy the signing process wouldn’t fail, what would fail would be the verification on devices, not allowing the build to be installed.

I think it might be related to either hidden files not being sent to the compiling process on ansca’s part and being used on our part, or the opposite. This makes it so that the contents of the project are a bit different in both stages resulting is signature mismatching.

I have no idea this is the real reason or even if that is the reason for you, but for us removing every single hidden file worked. (version control files/directories, file backups that some software creates when you modify a file, and so on)

Manuel [import]uid: 61899 topic_id: 23232 reply_id: 92995[/import]

#7

Hey, sorry - different time zones :wink:

  1. If you have an app built fine already you don’t need to touch your certificates, although doing so now would not effect the one in review it is NOT needed.

  2. Sample apps - the hello world example can you build that, not just run in simulator but build it properly, and let me know what happens.

The certificate you use to build it should probably be distribution with an AdHoc (NOT store) profile.

Can you let me know how that goes?

For future reference our support page does have Corona 102, a service for this kind of thing. (Although naturally will do my best to help you here.)

Peach :slight_smile: [import]uid: 52491 topic_id: 23232 reply_id: 92996[/import]

#8

I just yesterday resolved a codesign failure thing that started when my working AdHoc distribution profile expired Sunday.

What finally helped me get things working again was finding the Apple Technical Note TN2250: Code Signing in a nutshell. It’s at https://developer.apple.com/library/ios/#technotes/tn2250/_index.html

But then in addition, since my device had been upgraded to iOS 5.1 after the iPad announcement, I had to update xCode to 4.3.1 so the xCode Organizer could talk to it again, and then that required that I get a later daily build of Corona SDK to work with that new xCode SDK. [import]uid: 23636 topic_id: 23232 reply_id: 93025[/import]

#9

Thanks Martin - I touched base with your ‘set to default’ advise from an earlier thread by the way - all useful stuff.

Yes, since the start of the codesign issue I changed to 5.1 on the iPad myself, so I’ve no doubt complicated the issue. I’ve come across the developer notes you mention and look forwards to the day when I can understand them.

In the meantime, I tried deleting and installing new prov/dist profiles and, I’m embarrassed to say, noticed I didn’t have the full bundle identifier with the app in question. When I did new profiles to that app ID, although the developer profile through up the same message, the dist profile said the app was good to go. So, I’m giving the little blighter one more check and then I’ll try sending it on its way. Fingers crossed.

I’m not presuming for a moment that I’ve got off that lightly though. [import]uid: 94653 topic_id: 23232 reply_id: 93027[/import]

#10

threw, not through! [import]uid: 94653 topic_id: 23232 reply_id: 93028[/import]

#11

And have you indeed got off that lightly? I’m hoping so! :slight_smile: [import]uid: 52491 topic_id: 23232 reply_id: 93203[/import]

#12

Mornin’ Peach (evening for you?), yeah ripper, thanks.

Although, having deleted unnecessary profiles in Xcode, the names still appear in the Corona > Build for iOS > Code ID (Choose from the Following) roll-over-drop-down-pop-up thingie.

Also, there are still duplications of a couple of the profiles, which is an anomaly that was happening before the codesign issue. It’s like Corona has a cache that isn’t being cleared. Totally guessing though.

; ) [import]uid: 94653 topic_id: 23232 reply_id: 93228[/import]