Codesigning failed

Getting into LiveCode for iOS? Ask your questions here.

Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller

Post Reply
Pistris
Posts: 148
Joined: Mon Jul 20, 2015 2:40 am

Codesigning failed

Post by Pistris » Thu Aug 20, 2015 8:51 pm

Just now am getting
"codesigning failed with warning -- resource - rules has been deprecated in MAC OS X >= 10.10
CSSM_SignData returned: 800108E6
/Users/eduardo/Desktop/MobileBrowser/MobileBrowser.app:
errSecInternalComponent

i have saved apps today and tested them with no problems
havent made any updates to the OS or LC or xcodeo

this error happens for all the apps i have
and only happens while trying to build the stand alone
thay all work fine in the simulator

any thoughts?

LCNeil
Livecode Staff Member
Livecode Staff Member
Posts: 1223
Joined: Wed Oct 03, 2012 4:07 pm

Re: Codesigning failed

Post by LCNeil » Fri Aug 21, 2015 8:19 am

According to this post http://forums.livecode.com/viewtopic.php?f=8&t=22491, it sounds like an issue with your certificates/profiles. I would try revoking your current ones, deleting them from your system and generating new ones

Kind Regards,

Neil Roger
--
LiveCode Support Team ~ http://www.livecode.com
-

Pistris
Posts: 148
Joined: Mon Jul 20, 2015 2:40 am

Re: Codesigning failed

Post by Pistris » Fri Aug 21, 2015 1:35 pm

Hi Neil

i have another mac that has the same software and certificates installed and is working fine
i dont use that mac cause its an old 13 inch macbook , the screen is very small

i did what was suggested int he thread you shared minus the keychain part
i dont even know what a keychain is

thanks

LCNeil
Livecode Staff Member
Livecode Staff Member
Posts: 1223
Joined: Wed Oct 03, 2012 4:07 pm

Re: Codesigning failed

Post by LCNeil » Fri Aug 21, 2015 2:01 pm

Any certificate you create are stored in your Macs keychain assistant. Keycahin, in simple terms, can basically be seen as a password manger.

The easiest way to launch keychain is by typing "Keychain" into spotlight.

More information on the certificates stored in your keychain (and how to mange them) can be found here

https://developer.apple.com/library/pre ... cates.html

Kind Regards,

Neil Roger
--
LiveCode Support Team ~ http://www.livecode.com
-

Pistris
Posts: 148
Joined: Mon Jul 20, 2015 2:40 am

Re: Codesigning failed

Post by Pistris » Sat Aug 22, 2015 12:21 am

Thank you Neil

I couldn't figure out what the problem was so i reintalled xcode and everything is working again

by the way how can i check if a specific bug has been resolved/fixed

i want to install xcode 6.4 with LC 7.1 but i cant get to connect to MySQL

thanks

HAnil
Posts: 13
Joined: Fri Oct 24, 2014 10:14 am

Re: Codesigning failed

Post by HAnil » Sat Mar 26, 2016 5:34 am

I have a problem when signing app.
"codesigning failed with Warning: —resource-rules has been deprecated in Mac OS X >= 10.10!
Signed app bundle with Mach-O universal (armv7 arm64)"
I called the forum. I tried the suggestions.
I erased and re-create certificates. but did not resolve the error.
What could you suggest? do you have faced before?
Thank you for your interest
______________________________________________

do you have a suggestion?

tibinta
Posts: 6
Joined: Fri Apr 22, 2016 12:52 pm

Re: Codesigning failed

Post by tibinta » Fri Apr 22, 2016 6:32 pm

Yes, I have the same problem :( Any fix?

Pistris
Posts: 148
Joined: Mon Jul 20, 2015 2:40 am

Re: Codesigning failed

Post by Pistris » Fri Apr 22, 2016 7:02 pm

It has been resolved in the release candidate
just install the new version

you can also keep using your version since even though you get the error the app builds fine and you can install it on the phone

edd.

tibinta
Posts: 6
Joined: Fri Apr 22, 2016 12:52 pm

Re: Codesigning failed

Post by tibinta » Fri Apr 22, 2016 7:07 pm

I have 8.00 RC1 already :( No luck, if it builds how can I put it on my device from LiveCode, only by selecting my iphone from devices and adding the app manually to Installed Apps, no auto way as in xCode??

dave.kilroy
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 858
Joined: Wed Jun 24, 2009 1:17 pm
Location: Plymouth, UK
Contact:

Re: Codesigning failed

Post by dave.kilroy » Fri Apr 22, 2016 7:18 pm

Hello all - if you are experiencing the 'MACH-O' bug then the fix for it is detailed by Panos here http://quality.livecode.com/show_bug.cgi?id=17292 and it is also discussed in this thread http://forums.livecode.com/viewtopic.ph ... 8&start=15

There are a couple of issues going on, don't rush and take your time - don't forget that when you fix the MACH-O bug by amending the revsaveasiosstandalone stack that you CANNOT SAVE IT (because its in the LiveCode app bundle - new security restrictions), once you've made the changes outlined by Panos just click 'file' and 'apply' - you will then be able to build for iOS until the next time you restart LiveCode (I've been building for iOS with LC8.0(rc1) and Xcode 7.3 all week...)

Dave
"...this is not the code you are looking for..."

Pistris
Posts: 148
Joined: Mon Jul 20, 2015 2:40 am

Re: Codesigning failed

Post by Pistris » Fri Apr 22, 2016 9:51 pm

After i upgraded to rc1 i haven't had that warning popup, go figure

i thought it was resolved

Edd.

jacque
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 7214
Joined: Sat Apr 08, 2006 8:31 pm
Location: Minneapolis MN
Contact:

Re: Codesigning failed

Post by jacque » Sat Apr 23, 2016 5:41 pm

tibinta wrote:I have 8.00 RC1 already :( No luck, if it builds how can I put it on my device from LiveCode, only by selecting my iphone from devices and adding the app manually to Installed Apps, no auto way as in xCode??
LC 8 rc2 fixes the codesigning issue.
Jacqueline Landman Gay | jacque at hyperactivesw dot com
HyperActive Software | http://www.hyperactivesw.com

dave.kilroy
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 858
Joined: Wed Jun 24, 2009 1:17 pm
Location: Plymouth, UK
Contact:

Re: Codesigning failed

Post by dave.kilroy » Sat Apr 23, 2016 6:11 pm

They haven't released LC8.0(rc2) yet - but when it comes I think it will fix this bug :)
"...this is not the code you are looking for..."

Post Reply

Return to “iOS Deployment”