Search Issue Tracker

Fixed in 2021.2.X

Fixed in 2020.3.X, 2021.1.X

Votes

1

Found in

2020.3.0f1

Issue ID

1324168

Regression

Yes

Resigning Unity built macOS app results in "code signature data out of place" out of place error

MacOS

-

Repro steps:

1. Get a project with one or more native plugins;
2. Built it for macOS standalone;
3. Try to resign it using "codesign --force --sign - --preserve-metadata=identifier,entitlements,flags --timestamp=none --deep 'path/to/game.app'"
4. Observe the error:

/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/codesign_allocate: fatal error: file not in an order that can be processed (code signature data out of place): /Users/User/Desktop/Product.app/Contents/PlugIns/lib_burst_generated.bundle

Comments (7)

  1. E5069cd4e87243c209762451cf564b74?d=mm

    shubear

    Apr 19, 2021 06:36

    Same issue on P31iCloudPlugin.bundle on 2020.3.4f1

  2. D492be3777561a479e351d1c860f4eef?d=mm

    joonturbo

    Apr 16, 2021 12:48

    encountering this issue with P31iCloudPlugin.bundle on 2020.3.2f1

  3. 5c854200307bfdd5d7e9979495b610cd?d=mm

    RichardTea

    Apr 16, 2021 09:52

    I was previously aware of this other related issue:
    https://issuetracker.unity3d.com/issues/macos-builds-now-contain-a-quarantine-attribute

    However, the interaction of these two issues means that it is currently impossible to ship a Unity 2020.3 macOS build!

  4. 63d65848c74ab5fce031f759ccbf185b?d=mm

    bryangale

    Apr 13, 2021 17:06

    Seeing something very similar. Specifically on Debug macOS (Intel only) builds I see:

    /Library/Developer/CommandLineTools/usr/bin/codesign_allocate: fatal error: file not in an order that can be processed (code signature data out of place): [PROJECT PATH]/[APP NAME].app/Contents/Frameworks/UnityPlayer.dylib

    I don't see this for Release macOS (Intel only) builds

  5. Ca3592d3c81e46686f9d39f91c9a52fc?d=mm

    AbsurdAndy

    Apr 13, 2021 16:55

    Though this is listed as "Fixed in 2020.3.x" this fix is NOT included in 2020.3.0, 2020.3.1, 2020.3.2, or 2020.3.3 (the latest so far).

  6. 1e76a7a6a37dbf9edf0b9038f49a2d15?d=mm

    SuperMilkGuild

    Apr 12, 2021 10:10

    We are getting the same issue.

    In Unity 2030.3.2f1 and also tried in the
    Unity 2021.1.2f1

    Is the generated bundle being created with support for both the require MacOS architectures?
    x86_64 and arm64?

  7. 27b3e03ff6967a3636ee2bde72ef2cad?d=mm

    zingperformance

    Mar 31, 2021 15:31

    Is this problem fixed in Unity 2021.1.1f1??

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.