LiveCode Forums.

when I build app for iPhone, I have a problem that

"codesigning failed with Warnings: --resource-rules has been deprecated in MAC OS X 10.10! /Users/Anil/Untitled 13/Untitled 1.app: signed app bundle with Mach-O universal (armv7 arm64) [com.yourcompany.yourapp]"

After than this window seems

"There was an error while saving the standalone application codesigning failed with Warnings: --resource-rules has been deprecated in MAC OS X 10.10! /Users/Anil/Untitled 13/Untitled 1.app: signed app bundle with Mach-O universal (armv7 arm64) [com.yourcompany.yourapp]"

I searched NET but I have not found a solution.
I erased all the certificates and re-creates. changing nothing happened.

I installed new OSX 10.10.5 in vmware fusion and installed xcode 7.2 and livecode 8 and I tried to build this one without problems. it works.
but as soon as the upgrade to OSX 10:11 I get same error.

Thank you in advance for the help.

FWIW, I have exactly the same issue, which hasn't been solved by trying any of the suggestions in this http://forums.livecode.com/viewtopic.php?f=49&t=25113 thread.

Peter.

I guess, LiveCode 8.0 Dp17 will solve this problem

Hi @hAnil and @creepyTowel

I noticed you didn't seem to be getting any support in what you were experiencing - so after a quick search found that you get better results for "Mach-O" instead of "Mac-O" in Anil's error string.

--resource-rules has been deprecated in MAC OS X 10.10! /Users/Anil/Untitled 13/Untitled 1.app: signed app bundle with Mac-O universal (armv7 arm64) [com.yourcompany.yourapp]"

I then decided to find out what "Mach-O" was (had never heard of it) and found this page https://en.wikipedia.org/wiki/Mach-O from wikipedia.

All very interesting, but no direct clue as to where the 'smoking gun' might be in how LiveCode was interacting with OS X to get you that error. I was about to do some more investigating when I received this week's "This Week In LiveCode" from Peter Brett https://livecode.github.io/this-week-in ... de-27.html, inside which was a "Fix OS X code signing on El Capitan 10.11.4" link which led to https://github.com/livecode/livecode/pull/3817.

So, it seems that the issue was addressed five days ago by Fraser and will hopefully appear in the next version of LiveCode. I'm still rather vague as to what exactly the problem was (not enough time to read the Wikipedia article properly) but with any luck what Fraser has done means I won't have to!

Kind regards

Dave

Thanks for the very clear explanation, Dave -- much appreciated. Let's hope it's sorted in DP17.

Cheers

I guess then the question is.. "When will dp17 appear ?"

Now I've got the bug too!

Hi all,

Anil has reported a bug about this issue (bug 17292).

However, I cannot reproduce it on my OS X 10.11 machine. It would be useful if you could post an update on the bug report, if the suggestion in comment 6 of the bug report does not help. Please also mention which version of LiveCode/Xcode you use.

Best,
Panos
--

PS: LC forums does not allow me to post a link, no idea why

Hi Newbie,

LiveCode_Panos wrote:...
PS: LC forums does not allow me to post a link, no idea why

you need to have at least 10 postings before you can post links etc.


Best

Klaus

When I used the suggestion from the bug report, the xcode-select command returned the correct path to Xcode 7.2.1. Needless to say, I still get the error.

I noticed I was also linking to Xcode 5.1.1 in Livecode Preferences. This version doesn't work on El Capitan, but even removing it from Preferences didn't resolve the problem, so that's not the cause.

I presume this is not going to be fixed in DP 17 unless someone at Livecode can reproduce this problem?

Currently I and, I presume, others can't create iOS standalones, so this is quite worrying.

Adrian.

Edit:-
P.S. Panos - are you on OSX 10.11.4? (Wondering if the .4 is significant).
P.P.S. How does this inability to reproduce the problem tie in with the pull request Dave referenced above?

Hi all

I've just added a comment to the bug report http://quality.livecode.com/show_bug.cgi?id=17292 (actually didn't know there was a bug report) - maybe if others here also add their voice to the bug report it will help to get things moving...

Kind regards

Dave

Hi all,

I have posted a workaround in the bug report. Please let us know if it works, since I am not on OSX now.

@Adrian: The El Capitan machine I tested was running 10.11.2 and at some point I upgraded to 10.11.5. To be honest, I do not remember if I had tested before or after the upgrade. I will test again tomorrow. If the workaround fixes the problem, I will submit a pull request.

Best,
Panos
--

I was seeing the same warnings on OS X 10.11.4 with LC8.0.0 (dp16) and Xcode 7.2.1, but the app still built and loaded onto my iPad OK, so I just ignored the warnings until I had time to investigate, however the fix you posted works fine for me.

Thank you.

Paul

Hi all, if you visit the bug report you'll see that Panos posted a work-around that gets us building for iOS again - thanks Panos!

Yep, it works for me, too.

Thanks Panos.