"Disallowed xattr com.apple.FinderInfo" error

[rcmills]

I am receiving a (new to me) error while trying to compile a simple game app into iOS.

It reads:

There was an error while saving the standalone application codesigning failed with /Users /rcmills/Library/Mobile
Documents/com~apple~CloudDocs /Livecode stacks/MineSweep/iOS/MineSweep3/MineSweep.app: resource fork, Finder information,
or similar detritus not allowed file with invalid attached data: Disallowed xattr com.apple.Finderinfo found on /Users/rcmills /Library/Mobile Documents/com~apple~CloudDocs /Livecode stacks/MineSweep/iOS/MineSweep3/MineSweep.app

The app does not have any added inclusions or copied files, and the standalone app settings appear no different from many I have previously compiled.

I am using version 9.6.10 build 15611 of LC on my Mac Mini with Sonoma 14.1.2

Does anyone have any insights for me? Thanks!

[rayjbenet]

I am seeing the same error in 10.0.0 as well as 9.6.13 when compiling applications for MacOS.

I am running Sequoia 15.1 (24B83) on a MacBook Pro M1 machine (only since Sunday) I tried compiling three different apps and they all throw this error.

My last successful compiles were months ago in Sonoma and worked successfully.

The thread shown below on Apple community support seems to cover this topic somewhat thoroughly but doesn't provide (an obvious) solution - all of the technical bits they are calling out to investigate are happening "under the hood" in LiveCode. It seems related to code-signing, but is a bit hard to investigate as all of the build artifacts disappear after you click "OK" on the error message.

https://forums.developer.apple.com/forums/thread/687480

[rayjbenet]

Okay, under the heading of "FWIW but I don't completely understand how/why this became necessary..." - I got one of my builds to work (but not the other)

Background:
The LiveCode mainstack that was being built as a standalone has 3 "substacks" and includes 5 livecodescript stacks.

Results:
I did this from in Terminal app:
xattr -cr "WR Refunds Machine - v1-2.livecode"

Then I opened that file in LiveCode 10, and then did the standalone build, and it all worked.

About the file/app in question:
"WR Refunds Machine - v1-2.livecode" is the "main stack" of the project. I believed it might be the culprit because I did this earlier:
- create a new blank stack.
- put a button and a field on the card
- ran "save as standalone" - SUCCESS (i.e., the problem isn't likely LiveCode)
- then I added the above file (refunds machine) to the Standalone settings (so it appears under "Stack files in the application"
- ran "save as standalone" - get the detritus error again
- quit LiveCode; opened Terminal; navigated to the directory and ran the xattr -cr command on the file
- opened LiveCode; opened my stack; ran "save as standalone" - SUCCESS

Part 2:
- closed completely out of LiveCode 10
- came back in after doing the same xattr -cr command to another source file for a standalone
- did a "Save As Standalone" on this app and get the same detritus warning
- NOTE: this app has no included stacks. It does include a calendar widget, a segmented control widget, and a datagrid.
- the Refunds machine had a datagrid, a navbar widget and a browser widget
- tried it again, still failing

Still on the quest...

[LCMark]

@rayjbenet: So in the original post, the problem is almost certainly to do with the standalone being built in a folder controlled by iCloud - iCloud likes to add extended attributes to files, and these are incompatible with codesigning. The solution there is to target a folder which isn't being controlled by iCloud for building the standalone.

[rcmills]

Yes, I was trying to save into an iCloud folder. I am sure that is the answer to my problem, though I can’t check it out right now.

Many thanks!!

[rayjbenet]

@rayjbenet: So in the original post, the problem is almost certainly to do with the standalone being built in a folder controlled by iCloud - iCloud likes to add extended attributes to files, and these are incompatible with codesigning. The solution there is to target a folder which isn't being controlled by iCloud for building the standalone.

Thanks a mil - absolutely the problem.

I opened the livecode file, did a build to confirm the error still got thrown. It did (my Documents and Desktop folders are both fully "iCloud" participants. My build directory was in the MyLiveCode folder in Documents.)

I made a copy of my existing builds folder under my user account in the Users directory. (/Users/rjb/non-iCloud stuff/rjb_builds). This is not on the iCloud Drive.

Went back into the livecode file and changed the build directory to that and it worked straight away.
Problem solved. Thanks for the insight Mark!