Falling at the last fence...
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
Falling at the last fence...
I have an app ready to upload to Apple for review through iTunes connect... but when I try and use the Application Loader to upload, I get a message ' Application failed codesign verification. The signature was invalid, or it was not signed with an iPhone distribution Certificate'...
I can see the 'iphone developer' & 'iphone distribution' certificate in the keyChain app and am told that they are both valid, so assume that something is not 'connected' correctly'.... anyone been through this grim experience that might have some insight into this problem ?
Dixie
I can see the 'iphone developer' & 'iphone distribution' certificate in the keyChain app and am told that they are both valid, so assume that something is not 'connected' correctly'.... anyone been through this grim experience that might have some insight into this problem ?
Dixie
- Attachments
-
- Shots001.png.zip
- (36.92 KiB) Downloaded 364 times
Re: Falling at the last fence...
Hi Dixie,
I never did try to upload a stack to Apple. From memory there were similar error messages reported when the app was not zipped before trying to upload. Just an idea.
All these hoops, shudder...
Kind regards
Bernd
I never did try to upload a stack to Apple. From memory there were similar error messages reported when the app was not zipped before trying to upload. Just an idea.
All these hoops, shudder...
Kind regards
Bernd
-
- Posts: 83
- Joined: Mon Oct 31, 2011 5:28 am
Re: Falling at the last fence...
the steps I followed:
0) create an app id in the provisioning portal, use the format teamid.* so it'll be something like EDFGSHSGEY6.*
1) Generate a single certificate using keychain request certificate from a certificate authority. Use your email address associated with your iOS developer account, and the name you signed up using, save to disk option. oh first setting keychain prefs to certificates - OCSP off CRL off. You're going to use this certificate for both dev & distribution.
2) In the provisioning portal click on the development tab, upload your certificate (from wherever you saved it to). Re-click on certificates and your certificate should now be available for download. Download it + the WWDR certificate. Double click on each individually to load them into keychain.
3) in certificates, click on distribution. Do the same as 2), download then doubleclick. (I think the WWDR cert is the same for both so can probably skip that for distribution)
4) switch to the provisioning tab, you need to do the following for both the development and distribution tabs). Click the new profile button. Give it a unique name (like "my App development provisioning" and "my App distribution provisioning"). Select the certificate you uploaded (will be a checkbox with your name if it looks like my screen. Select the App id you created in step 0), then click submit.
5) Click on the provision tab again and your profiles should be available for download. Download both the dev and distro versions to you machine somewhere
6) Open up Xcode and switch to the organiser. Deselect automatic device provisioning. Drag in the two provisioning profiles you downloaded in 5)
7) Open up live code and select the distribution profile in the standalone IOS setting screen. You must also have the same app ID as step 0)
8 ) Create your app, then zip if up by right clicking on it and selecting compress xxxx.app
9) open up application loader, enter your developer credentials. Navigate to your newly created zip file (application loader only accepts a zip file). Hold your breath and click submit. it'll take a little while, seems to have quite a few steps it goes through but they're all automatic.
0) create an app id in the provisioning portal, use the format teamid.* so it'll be something like EDFGSHSGEY6.*
1) Generate a single certificate using keychain request certificate from a certificate authority. Use your email address associated with your iOS developer account, and the name you signed up using, save to disk option. oh first setting keychain prefs to certificates - OCSP off CRL off. You're going to use this certificate for both dev & distribution.
2) In the provisioning portal click on the development tab, upload your certificate (from wherever you saved it to). Re-click on certificates and your certificate should now be available for download. Download it + the WWDR certificate. Double click on each individually to load them into keychain.
3) in certificates, click on distribution. Do the same as 2), download then doubleclick. (I think the WWDR cert is the same for both so can probably skip that for distribution)
4) switch to the provisioning tab, you need to do the following for both the development and distribution tabs). Click the new profile button. Give it a unique name (like "my App development provisioning" and "my App distribution provisioning"). Select the certificate you uploaded (will be a checkbox with your name if it looks like my screen. Select the App id you created in step 0), then click submit.
5) Click on the provision tab again and your profiles should be available for download. Download both the dev and distro versions to you machine somewhere
6) Open up Xcode and switch to the organiser. Deselect automatic device provisioning. Drag in the two provisioning profiles you downloaded in 5)
7) Open up live code and select the distribution profile in the standalone IOS setting screen. You must also have the same app ID as step 0)
8 ) Create your app, then zip if up by right clicking on it and selecting compress xxxx.app
9) open up application loader, enter your developer credentials. Navigate to your newly created zip file (application loader only accepts a zip file). Hold your breath and click submit. it'll take a little while, seems to have quite a few steps it goes through but they're all automatic.
Re: Falling at the last fence...
Thanks for the replies.. Andy, Mark & Ken on the use-livecode list and colourPixels here on the forum (Oh yes, and to Bernd for at least taking pity on me) I cannot now say what went wrong or what happened, all that I can tell you is that I spent more than 6 hours trying to sort it all out... the chaos descended into problems with the keychain and with xCode... it got to the point where the binary would not even load onto the iphone... the eventual solution was to clear 'everything' out of the keychain that was iOS related, dumped 'everything' out from xCode and started the whole business from scratch through the Apple Developer website...
But a big 'shout' for John Craig who kept me calm and managed to talk me out of throwing my Mac out into the rain, paitently helping me through the problem... (My God!.. 'Skype' is marvelous, I can't imagine how I ever survived in the past without it)... but on a serious note, I would just like to say that 'Apple' have made a complete 'bollocks' of uploading apps onto a device never mind trying to get it to their 'review team'...
take care...
Dixie.
But a big 'shout' for John Craig who kept me calm and managed to talk me out of throwing my Mac out into the rain, paitently helping me through the problem... (My God!.. 'Skype' is marvelous, I can't imagine how I ever survived in the past without it)... but on a serious note, I would just like to say that 'Apple' have made a complete 'bollocks' of uploading apps onto a device never mind trying to get it to their 'review team'...
take care...
Dixie.
Re: Falling at the last fence...
Been there, done thatDixie wrote: the eventual solution was to clear 'everything' out of the keychain that was iOS related, dumped 'everything' out from xCode and started the whole business from scratch through the Apple Developer website...

g
14" MacBook Pro
Former LiveCode developer.
Now recovering.
Former LiveCode developer.
Now recovering.
Re: Falling at the last fence...
Ah, the agony and the joy- mostly agony. I've struggled with this as well, including not being able to upload updates to an app that I'd uploaded before. There are numerous threads (e.g. http://forums.runrev.com/viewtopic.php? ... ign#p48407) cataloging all of the pain. After spending more hours on this than I want to admit, I believe that a bug in Keychain Access related to expired certificates is the culprit. At least I desperately hope it is. The next time someone has this issue, it would be very helpful if they could try the fix described here:
http://red-glasses.com/index.php/iphone ... ly-be-one/
If it works, please let us know.
http://red-glasses.com/index.php/iphone ... ly-be-one/
If it works, please let us know.
Re: Falling at the last fence...
I submitted my iPad/iPhone application today and they accepted it and I am waiting for approval. It took me about 3 hours to get a distribution profile, resize some of my screenshots, get a 512 x 512 icon, type in my program description, set my price tier, change the standalone application settings, rebuild a distribution standalone, figure out where to find the uploader in x-code, zip the file, and upload the application. Hoping next time to shave some time off that.
Fingers crossed. Thanks for all your help!
Dave
Fingers crossed. Thanks for all your help!
Dave
Re: Falling at the last fence...
I'm in the same boat as Dixie. I may have to start from scratch again.
How frustrating to be so close to the end and get this huge roadblock.
Max
How frustrating to be so close to the end and get this huge roadblock.
Max
Re: Falling at the last fence...
As I finally creep up to the final step, and upload my app, I wait patiently for 20 minutes for it to upload, in order to get the message invalid binary with no additional help.
After painstakingly rereading the Live code directions in their lessons section for creating a certificate going through this process 6 more times with the same result, it's probably time to kill myself.
As an alternative, perhaps there is some kind soul out there that can offer assistance.
Max
After painstakingly rereading the Live code directions in their lessons section for creating a certificate going through this process 6 more times with the same result, it's probably time to kill myself.
As an alternative, perhaps there is some kind soul out there that can offer assistance.
Max
Re: Falling at the last fence...
I am in the exact same situation and have been at it for a total of atleast 10 hours trying to figure out how to get around this error. Getting the same one Dixie mentioned in the Application Loader:
"Application failed codesign verification. The signature was invalid, contains disallowed entitlements, or it was not signed with an iPhone Distribution Certificate."
I have trouble shooted the following:
1. Checked and made sure that my Bundle IDs matched up with my LiveCode project and my distribution certificate.
2. Deleted both my iPhone Developer certificate and my iPhone Distribution certificates and requested completely new ones.
3. Deleted all of my provisioning profiles and created completely new ones.
4. Checked to make sure that my app in iTunes Connect is "Waiting for Upload" (and it is)
5. Made sure that none of my certificates are expired (none of them are, they are all active and valid.
6. Made sure that my standalone app was zipped up using Finder>Compress and not another software like Stuffit.
Pretty much anything I could think of shy of uninstalling and reinstalling livecode, xcode, and lion all together.
I'm currently running LiveCode 5.0.2, creating an iPad application.
Running Mac OS X Lion 10.7.3
Xcode 4.2.1
Application Loader 2.5.1
Anyone have any further suggestions on how I can simply deliver my app? This has become a huge headache. Thanks in advance.
"Application failed codesign verification. The signature was invalid, contains disallowed entitlements, or it was not signed with an iPhone Distribution Certificate."
I have trouble shooted the following:
1. Checked and made sure that my Bundle IDs matched up with my LiveCode project and my distribution certificate.
2. Deleted both my iPhone Developer certificate and my iPhone Distribution certificates and requested completely new ones.
3. Deleted all of my provisioning profiles and created completely new ones.
4. Checked to make sure that my app in iTunes Connect is "Waiting for Upload" (and it is)
5. Made sure that none of my certificates are expired (none of them are, they are all active and valid.
6. Made sure that my standalone app was zipped up using Finder>Compress and not another software like Stuffit.
Pretty much anything I could think of shy of uninstalling and reinstalling livecode, xcode, and lion all together.
I'm currently running LiveCode 5.0.2, creating an iPad application.
Running Mac OS X Lion 10.7.3
Xcode 4.2.1
Application Loader 2.5.1
Anyone have any further suggestions on how I can simply deliver my app? This has become a huge headache. Thanks in advance.
Re: Falling at the last fence...
I had a similar problem because old certificates were in my keychain and somehow it did not do the link with the new ones (I mean LC while building the standalone)
So as an added step, open keychain, delete other apple certificates (or all of them before you reinstall the fresh ones) and rebuild your standalone. It should ask you for an authorization (admin access) to use keychain, which proves that you use the right certificate.
It worked for me. Waiting for the green light on the App store for my first update to my first app already accepted.
Hope it helps
So as an added step, open keychain, delete other apple certificates (or all of them before you reinstall the fresh ones) and rebuild your standalone. It should ask you for an authorization (admin access) to use keychain, which proves that you use the right certificate.
It worked for me. Waiting for the green light on the App store for my first update to my first app already accepted.
Hope it helps
Re: Falling at the last fence...
Expired certificates seem to be the most common (sadly, not the only) cause of this error. The problem is compounded by a bug in Keychain access. Once again, please read this for some tips:
http://red-glasses.com/index.php/iphone ... ly-be-one/
Even though the error message is different, for me the bug related to seemingly deleted old certificates has been the culprit.
http://red-glasses.com/index.php/iphone ... ly-be-one/
Even though the error message is different, for me the bug related to seemingly deleted old certificates has been the culprit.
Re: Falling at the last fence...
OK after 2 weeks of juggling Livecode, xcode, download helper, keychain access, itunes connect, and ios dev center just to be able to upload my app. This includes struggling through many videos, lessons, forum comments, xcode docs, and ios dev docs.
I just want to be able to upload my app!
I just want to be able to upload my app!
Re: Falling at the last fence...
And has anyone every used Itune connent support?
First, there is no support. I click on the "Contact Us" button and all you get is troubleshooting help that doesn't even get close to the problem you are having.
First, there is no support. I click on the "Contact Us" button and all you get is troubleshooting help that doesn't even get close to the problem you are having.
Re: Falling at the last fence...
And my Application Loader has stopped working because it says it is incompatible with Mac system 10. I wonder how that happened overnight?