Deprecated Error

Getting into LiveCode for iOS? Ask your questions here.

Moderators: heatherlaine, Klaus, FourthWorld, robinmiller, kevinmiller

Post Reply
Posts: 6
Joined: Wed Jan 13, 2016 6:18 pm

Deprecated Error

Post by salana46 » Sat Apr 22, 2017 3:33 pm

I am getting an error when trying to create a standalone file.

I am using:
Livecode 7.1.1
Mac OS X El Capitan 10.11.6
Xcode 7.1.1

The error says code signing failed with warning. I have attached a screen shot of the error.

I messaged the Livecode team and got this reply.

"Thank you for your request. Apparently this is related to your version of Xcode
and OS.

Since Xcode 7, the Code Signing Resource Rules Path build setting must be left
empty or else this warning is produced.

Technical Note TN2206 provides the details:

Resource Rules
Systems before OS X Mavericks v10.9 documented a signing feature (--resource-
rules) to control which files in a bundle should be sealed by a code signature.
This feature has been obsoleted for Mavericks. Code signatures made in
Mavericks and later always seal all files in a bundle; there is no need to
specify this explicitly any more. This also means that the Code Signing
Resource Rules Path build setting in Xcode should no longer be used and should
be left blank"

I can't seem to find what they are referring to. Can anyone help?
deprecated error.tiff
deprecated error.tiff (34.93 KiB) Viewed 609 times

Livecode Staff Member
Livecode Staff Member
Posts: 388
Joined: Fri Feb 06, 2015 4:03 pm

Re: Deprecated Error

Post by LiveCode_Panos » Sun Apr 23, 2017 8:55 am

Hi salana46,

This is a bug in LiveCode 7.1.1 on El Capitan, which was fixed in LiveCode 7.1.4.

The bug happens because the standalone builder identified a successful codesign if the result of the codesign command contained the keywords "signed bundle". However, at some point on El Capitan, a successful codesign returned "signed app bundle" rather than "signed bundle", and this confused the standalone builder.

See this bug report for more details. In comment 9 of this report there is a workaround you can apply to fix this bug locally in LiveCode 7.1.1, although I would recommend you use a newer LiveCode version (e.g. LiveCode 8.1.3) which is not affected by this bug, and also has much more new features.

Best regards,

Post Reply

Return to “iOS Deployment”