resource fork, Finder information, or similar detritus not allowed

Solar2D iOS
#21

I try it with the current daily build 2016.2983

maybe this will help, I did a compilation this morning BuildID: 58197c6caa15d on the build server but have the same problem.

#22

Try using the latest daily build.

Rob

#23

I have tried the latest build but always have the same problem. could it be that this error happens only with Xcode 10.1 ?

#24

sorry not Xcode 10.1, is use 8.1!

#25

Can you post the entire console log from your build?

Thanks

Rob

#26

Apple has this to say:

https://developer.apple.com/library/content/qa/qa1940/_index.html

We fixed this in 2950:

CoronaSDK 2016.2950

Post date:Fri, 2016-09-16 05:48

Release notes for build 2016.2949 through 2016.2950

  • iOS, tvOS: fixed issue where codesigning would sometimes fail due to “resource fork, Finder information, or similar detritus not allowed”

The log above shows that 2949 was used. Is anyone having this issue that’s using 2950 or later?

Rob

#27

Problem is solved, my IDE has used the wrong folder for compiling the project. it was always used the build 2949. I have fix this and now it build with the version 2984 and now it works perfect. 

#28

I’m still getting this error in Daily build 2994.

EDIT:

Ok, I figured out what was causing this and how to fix it. It’s due to Apple’s code signing process and their increased security around it.

When Corona creates a new iOS app, if there’s already an app file there it seems like it just overwrites data inside the package. It doesn’t actually delete the app file and start over. If Corona SDK actually did delete the app file before a build then no one would see this “detritus” error.

The error is mostly caused by using Finder to “Show Package Contents” on your iOS app. Finder will write some hidden information in the directory which the new code signing process doesn’t like (as it could be a new type of virus).

So, before starting an iOS SDK build, run Terminal and go to the directory where the app file is. Then run this command:

xattr -lr <name of your app file>

You should see something that looks like this:

com.apple.FinderInfo:

00000000  00 00 00 00 00 00 00 00 20 10 00 00 00 00 00 00  |… …|

00000010  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |…|

00000020

 

 

To get rid of this hidden information, type…

xattr -cr <name of your app file>

Then use Corona Simulator to build another iOS build.

#29

Thanks John. I’ll report this to Engineering and see if this is what’s happening. 

Rob

#30

We now copy only the changed files to the generated .app bundle.  If you have a project with many megabytes of assets this speeds up builds a lot.

I wasn’t able to reproduce the issue by doing a Show Package Contents  (maybe we’re on different versions of macOS; I’m on 10.12.1) but since macOS file attributes do give codesign indigestion I’ve modified the build process to strip them from the .app bundle before signing (we are already stripping them as the files are copied from the project directory but it appears this is insufficient).

It will be in Daily Builds CoronaSDK 2016.2995 and later

#31

Hi Perry,

I just updated to 2995 and made a SDK build – same error. 

I even deleted the app file first before building.

What could be causing this error?

#32

CoronaSDK 2016.2995 runs the xattr -cr <app-dir> command before calling codesign.

All I can suggest is running that on your source project directory but the Corona build process already avoids copying macOS extended attributes so something strange must be going on.

#33

@theromeo Great work finding this work-around. Can anyone here let me know when the latest build actually fixes this?