stevek
Aspiring developer
Profile
Posts: 808
Reg: Dec 24, 2011
great neck
8,080
04/22/12 07:23 PM (13 years ago)

Failed Code Sign, After a Long Time Without

I thought I was through with this nonsense. I was testing a new app, all going well. Don't know if this has anything to do with it but added armv6 and armv7 as I've done in all previous accepted apps, and now am getting warning: Application failed codesign verification. The signature was invalid, contains disallowed entitlements, or it was not signed with an iPhone Distribution Certificate. (-19011) I've put the build settings for this new app side by side with one just updated to Apple and accepted, no errors, and I see absolutely no differences with the code signing. And as I've said, I've built this new app dozens of times without a problem. I even went back and changed armv6 and armv7 to just armv6 but still no dice. Any ideas? Thanks.
 
Stobe
buzztouch Evangelist
Profile
Posts: 1528
Reg: Mar 04, 2011
Fredericksburg,...
24,680
like
04/22/12 08:56 PM (13 years ago)
Are you sure the build settings for your target are a valid distribution certificate? Are you intending to build to distribute or to test?
 
stevek
Aspiring developer
Profile
Posts: 808
Reg: Dec 24, 2011
great neck
8,080
like
04/22/12 09:33 PM (13 years ago)
At the moment i'm just testing and have been testing successfully for days on my devices. I will distribute later and have a distributor certificate too but i have been using the developer distributer certificate gotten a while back for other apps and it has been working fine up until today. I guess i'll probably have to delete all the certificates and get new ones if I can't figure this out. I've had to do this before with each new app it seems. Got to be a better way.
 
stevek
Aspiring developer
Profile
Posts: 808
Reg: Dec 24, 2011
great neck
8,080
like
04/22/12 09:50 PM (13 years ago)
I seem to have found an answer, though don't ask me why. The one setting that was different from a working app was in Build Settings. I had Validate Build Product set to on. Setting it to "no" got rid of the error. ???
 
Rad Doc
Apple Fan
Profile
Posts: 653
Reg: Oct 08, 2010
USA, NYC
8,580
like
04/28/12 01:14 PM (13 years ago)
Steve, For the first time in 2 years, i am facing the same issue. I cant for the life of me get rid of this error. Ive built and tested on multiple Apple devices and have had no problem. Now that i am trying to submit my app for distribution, i continue to get the error you mentioned. Do you have any suggestions where to go with this. I recently upgraded to lion and Xcode 4.3.2 from snow leopard, Xcode 4.2, which has no problems. I did what you suggested, but where did you change the setting, in project or target. Any help would be great. Anthony
 
stevek
Aspiring developer
Profile
Posts: 808
Reg: Dec 24, 2011
great neck
8,080
like
04/28/12 01:58 PM (13 years ago)
Anthony, I can just tell you my setting which seemed to work in this one case when I changed them: In Targets, under Build options, then under "validate built project" I have develop as "no" and release as "yes". In Project, in the same places, I have develop as "no" and release as "no". Don't remember which one of the four I actually changed to go from the error to no error but these are my final settings and all works with them. Good luck. Steve
 

Login + Screen Name Required to Post

pointerLogin to participate so you can start earning points. Once you're logged in (and have a screen name entered in your profile), you can subscribe to topics, follow users, and start learning how to make apps like the pros.