Build Error OS X 10.12 using Corona v.2016.2949

Getting Started Newbie Questions
#1

I’m getting:

ERROR: code signing failed: /Users/alexscarrow/Desktop/CUBEY KINGDOM DEV.app: replacing existing signature

/Users/alexscarrow/Desktop/CUBEY KINGDOM DEV.app: resource fork, Finder information, or similar detritus not allowed

 

I’m using:

 

Corona v.2016.2949

OS X = 10.12

 

I have all the right certs,provisioning profiles (I’m pretty sure anyway). I do get the warning that this version of Corona may produce unpredictable results with this OS X, I’m presuming this may be one of those results

#2

Here is a similar thread -> https://forums.coronalabs.com/topic/66282-resource-fork-finder-information-or-similar-detritus-not-allowed/#entry343053

#3

Please use a build 2950 or later.

Rob

#4

I’m using build 2992 (public) and Daily 2994 and I am always getting the “resource fork, Finder information, or similar detritus not allowed.” error.

I have to always make Enterprise builds now.

Could i be because i’m using XCODE 8.1?

#5

About 9 hours ago, for the first time, I am experiencing a similar problem…

ERROR: code signing failed: /Users/troylyndon/Documents/myAppName.app: resource fork, Finder information, or similar detritus not allowed

#6

We’ve taken about all the steps we can to prevent this. We are removing attributes on files that get copied over to the app bundle. The only thing is if the OS is adding resource forks to things behind the scenes like adding icons to folder icons or adding color labels etc.

We would really like to solve this, but we can’t reproduce it and we’ve taken steps to solve it to a point we don’t see the messages. 

What happens if you use the Terminal and do a cd into the .app bundle and run:

xattr -pr .

 

???

 

Maybe also try:  xattr -lr .

 

Rob

#7

I still get detritus every time the SDK makes a build – it happens during “Adding plugins…”

I basically sit in the Terminal just watching the build and running xattr -lr on the game until the junk gets in there, then i quickly run xattr -cr on it to clean it up.

#8

Hi John. What version of Corona SDK are you using? We added more things to build that scrubs the attributes in 3022.

And are you doing Simulator builds or Enterprise builds?

What is the target? iOS, macOS or tvOS?

Thanks

Rob

#9

This is an iOS target using build 3012.

The scrubbing needs to happen as the last thing before going to sign the app. Because while it’s adding plugins, the detritus appears.

#10

Hi John. Daily build 3022 has additional scrubbing of extended attributes.

Can you dry with that build or later?  I would recommend trying 3025 since it tightens up some plugin issues with the Corona Simulator and desktop builds.

Rob

#11

I just got 3025 and built an iOS version. Detritus error again.

#12

Here is a similar thread -> https://forums.coronalabs.com/topic/66282-resource-fork-finder-information-or-similar-detritus-not-allowed/#entry343053

#13

Please use a build 2950 or later.

Rob

#14

I’m using build 2992 (public) and Daily 2994 and I am always getting the “resource fork, Finder information, or similar detritus not allowed.” error.

I have to always make Enterprise builds now.

Could i be because i’m using XCODE 8.1?

#15

About 9 hours ago, for the first time, I am experiencing a similar problem…

ERROR: code signing failed: /Users/troylyndon/Documents/myAppName.app: resource fork, Finder information, or similar detritus not allowed

#16

We’ve taken about all the steps we can to prevent this. We are removing attributes on files that get copied over to the app bundle. The only thing is if the OS is adding resource forks to things behind the scenes like adding icons to folder icons or adding color labels etc.

We would really like to solve this, but we can’t reproduce it and we’ve taken steps to solve it to a point we don’t see the messages. 

What happens if you use the Terminal and do a cd into the .app bundle and run:

xattr -pr .

 

???

 

Maybe also try:  xattr -lr .

 

Rob

#17

I still get detritus every time the SDK makes a build – it happens during “Adding plugins…”

I basically sit in the Terminal just watching the build and running xattr -lr on the game until the junk gets in there, then i quickly run xattr -cr on it to clean it up.

#18

Hi John. What version of Corona SDK are you using? We added more things to build that scrubs the attributes in 3022.

And are you doing Simulator builds or Enterprise builds?

What is the target? iOS, macOS or tvOS?

Thanks

Rob

#19

This is an iOS target using build 3012.

The scrubbing needs to happen as the last thing before going to sign the app. Because while it’s adding plugins, the detritus appears.

#20

Hi John. Daily build 3022 has additional scrubbing of extended attributes.

Can you dry with that build or later?  I would recommend trying 3025 since it tightens up some plugin issues with the Corona Simulator and desktop builds.

Rob