Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

Xcode CodeSign fails on resource fork or Finder information

Errorresource fork, Finder information, or similar detritus not allowed

Short answer

Code signing refuses an app bundle when any file in it carries an extended attribute such as a resource fork or Finder info. List the attributes with xattr -lr on the bundle, clear them with xattr -cr, and build again. If they come back, a step in your build or a Finder action keeps adding them, so find that step.

  • Applies to Xcode 26, macOS 26
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    List the extended attributes on the built app. The files it prints are the ones that block signing.

    xattr -lr /path/to/MyApp.app
  2. 2Match what you see, then jump to its fix

    1. 1xattr -lr prints com.apple.FinderInfo (or a resource fork) for one or more filesFiles in the bundle carry resource fork or Finder info attributesFix
    2. 2Clearing works once, then the error returns on the next build or after you open the app in FinderSomething keeps adding the attributes backFix

What does the error look like?

  • resource fork, Finder information, or similar detritus not allowed
  • Command CodeSign failed with a nonzero exit code

Cause 1 of 2

Files in the bundle carry resource fork or Finder info attributes

1Check

Apple's QA1940 explains that code signing does not allow any file in an app bundle to have an extended attribute holding a resource fork or Finder information. List them to see which files are affected.

xattr -lr /path/to/MyApp.app

2Fix

Remove all extended attributes from the bundle, then sign again. If the files come from your source folders, clear them there too so every build starts clean.

xattr -cr /path/to/MyApp.app
xattr -cr /path/to/project/source-folder-with-resources

3Verify

The list command prints nothing, and the build signs without the error.

xattr -lr /path/to/MyApp.app

Confirmed by developer.apple.com

Did this fix it?

Cause 2 of 2

Something keeps adding the attributes back

1Check

QA1940 says that browsing inside a bundle with Finder's Show Package Contents can add Finder information to the files in it. It also tells you to audit your build process to find the step that adds the attributes instead of only clearing them by hand.

xattr -lr /path/to/MyApp.app | head

2Fix

Stop opening the built bundle in Finder. Find the Run Script, copy step or tool that touches the files and make it avoid adding attributes, or clear the attributes in the source files it copies.

# compare attributes on a source file and its copy in the bundle
xattr -l path/to/source/file
xattr -l /path/to/MyApp.app/file

3Verify

Build twice in a row without touching the bundle. Signing succeeds both times.

xcodebuild -project MyApp.xcodeproj -scheme MyApp -configuration Release build

Confirmed by developer.apple.com

Did this fix it?

How do I stop it coming back?

  • Do not open a built .app with Show Package Contents before it is signed.
  • Clear extended attributes on files you copy in from downloads or other Macs before adding them to the project.
  • Keep build steps that copy resources free of tools that add Finder metadata.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Related fixes

Mobile apps

App record creation fails because you lack permission

You cannot add a new app in App Store Connect as a Developer or limited user

Only the Account Holder, an Admin or an App Manager can create an app record, and Apple blocks it until the Account Holder has signed the latest agreement.

3 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.