11

Usually this comes up the first time I try to publish:

app/Japanese 5/iOS/bin/iPhone/Debug/Japanese.app: resource fork, 
Finder information, or similar detritus not allowed (Japanese.iOS)

My solution is always to do a clean all and then try again. So makes me wonder. Why does clean all solve the problem every time?

Does anyone know why this happens and what I can do to make it not happen?

3 Answers3

7

Code signing no longer allows any file in an app bundle to have an extended attribute containing a resource fork or Finder info.

To see which files are causing this error, run this command in Terminal:

$ xattr -lr <path_to_app_bundle>

replacing with the path to your actual app bundle.

And you can also remove all extended attributes from your app bundle with the xattr command:

$ xattr -cr <path_to_app_bundle>

For more information click here.

Pavan V Parekh
  • 1,906
  • 2
  • 19
  • 36
3

Seems it does not have to be necessarily related to Xamarin but rather to signing of application and so to iOS development itself. You could try already existing solutions for code signing issues in

Code Sign Error in macOS High Sierra Xcode - resource fork, Finder information, or similar detritus not allowed

or

Code Sign Error on macOS Sierra, Xcode 8

Hope it could help you.

Jaroslav Kadlec
  • 2,505
  • 4
  • 32
  • 43
0

There is a faster way to find files that have extended attributes, the -xattr find flag:

find . -type f -xattr -exec xattr -c {} \;
Zoe
  • 27,060
  • 21
  • 118
  • 148
Wooster
  • 101
  • 4