Search Unity

  1. We are migrating the Unity Forums to Unity Discussions. On July 12, the Unity Forums will become read-only. On July 15, Unity Discussions will become read-only until July 18, when the new design and the migrated forum contents will go live. Read our full announcement for more information and let us know if you have any questions.

Bug CodeSign failed with a nonzero exit code - Xcode 15, Unity 2022.3.10f1

Discussion in 'iOS and tvOS' started by voronwe13, Oct 3, 2023.

  1. voronwe13

    voronwe13

    Joined:
    Feb 23, 2017
    Posts:
    5
    I'm trying to build my project for iOS, and I believe I have everything set up correctly, but when I try building in XCode (whether I'm using a Device build or a Simulator build) it fails when trying to CodeSign the Unity Framework. When I look at the error message in the Reports, it says:

    /<path to app>/Frameworks/UnityFramework.framework: resource fork, Finder information, or similar detritus not allowed

    Command CodeSign failed with a nonzero exit code


    The only thing I can find for this error is to clear attributes using "xattr -cr ." but that doesn't fix the issue. Has anyone else come across this issue (I can't find any other reports in the forums), or have any idea how to fix it? Thanks!
     
  2. voronwe13

    voronwe13

    Joined:
    Feb 23, 2017
    Posts:
    5
    Turns out iCloud screws with the filesystem, even when everything is in a .nosync folder. I had Unity build the project to a folder outside of what iCloud backs up (i.e. not in Documents), and then the XCode project built just fine.