The application does not have a valid signature

12 replies [Last post]
tomreynolds
User offline. Last seen 37 weeks 4 hours ago. Offline
Joined: 27 Apr 2010

Hi,

I'm new here and may be missing something super obvious, but I just downloaded the trial Corona SDK and am trying to build a sample app to check out Corona. The app builds fine, I select 3.0 and use my Developer Provisioning Profile. However, when I go to install using either Xcode or iTunes I get the same error "The application does not have a valid signature". The app builds fine, and I've confirmed that I'm using a "Development" profile rather than an Ad Hoc or App Store one. A Google search only came up with: http://www.onidev.com/2010/01/12/the-application-does-not-have-a-valid-signature/ which doesn't seem relevant to my situation.

Any ideas?

Replies

MikeHart
User offline. Last seen 2 hours 45 min ago. Offline
Joined: 22 Mar 2010

Mmh,

the only idea I have is that the profile could be out of date (it lasts only 3 months) or not on your device anymore.

Cheers
Michael

carlos m. icaza's picture
carlos m. icaza
User offline. Last seen 3 hours 33 min ago. Offline
Ansca Staff
Joined: 22 Jun 2009

did you add your provisioning profile to your iphone, not just the app?

i use xcode organizer. there you have two panes. the provisioning profiles panes and an app pane. see if you can see if your provisioning profile is installed on the iphone properly.

Carlos

tomreynolds
User offline. Last seen 37 weeks 4 hours ago. Offline
Joined: 27 Apr 2010

Hi guys,

I probably should have clarified: building a non-Corona project using my development or ad hoc profile from Xcode works perfectly. I've also verified that the same profiles are on the iPhone and in Xcode. Tried building to my iPad as a test as well (which also works fine with native Xcode builds) and received the same error.

tomreynolds
User offline. Last seen 37 weeks 4 hours ago. Offline
Joined: 27 Apr 2010

I figured it out! It looks like the issue was due to the fact that I had both Xcode 3.2.2 and Xcode 3.2.3 installed (in separate directories). I guess Corona was building using the beta Xcode for some reason. Once I removed Xcode 3.2.3 Corona started giving an error that Xcode wasn't installed, telling me that it must have been using that version. Reinstalled Xcode 3.2.2 and the problem was solved!

cujino7
User offline. Last seen 2 weeks 2 hours ago. Offline
Joined: 23 Jan 2011

It's not working for me, even with different provisioning profiles, all up to date by the way. Building using Xcode works nicely on apps developed there.

I am using Xcode 3.2.5, is it because it only works with 3.2.2?

IgnacioIturra
User offline. Last seen 11 weeks 6 days ago. Offline
Joined: 31 Oct 2010

Make sure there are no spaces on the folders you're building to. I usually just stick to the desktop. Hopefully that's your problem.

rna_parts
User offline. Last seen 21 weeks 1 day ago. Offline
Joined: 12 Jan 2011

Trick 1: POST to the DESKTOP. if that works, then you can go back and look at your folder structure. remove all spaces in file folders...

techknight
User offline. Last seen 7 weeks 3 days ago. Offline
Joined: 30 Nov 2010

I just had this issue when building an app for a device for the first time.

It was definitely the space in the auto-generated default output folder name.

BlueDuckGaming
User offline. Last seen 12 weeks 2 days ago. Offline
Joined: 7 Jan 2011

I can Confirm that this was my Issue. My Game name has a space in it, and building the code to a subfolder under that directory caused the issue.

I built to desktop, and everything was fine. Anyway, just replying to add credit to this being the solution. Thanks!

Bug Report?

mauro8
User offline. Last seen 30 weeks 1 day ago. Offline
Joined: 23 Mar 2011

It's not working for me.
I'm using Xcode 4.0

Help me.

gamehkmail
User offline. Last seen 41 weeks 5 days ago. Offline
Joined: 15 Nov 2010

I found that code signing of Xcode does not support network account.
-- Advanced UI + Graph for Corona® | Website | Forum (https) | See:

mrvaibhavpanchal
User offline. Last seen 30 weeks 2 days ago. Offline
Joined: 1 Mar 2011

I am on XCode 4 and was stuck in the same issue.

Removing space in the build folder worked for me. The ouput folder was Desktop as suggested.

Thanks!

Viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.