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
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
Fixed in 2021.2.0a12, 2021.1.3f1 and 2020.3.5f1.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The Editor becomes unresponsive and memory allocation errors are spammed in the Console when Generating Lightning
- Crash on BatchApplyPropertiesFromSourceAssetDB when opening a specific project
- Scene view Camera cannot be moved with WASD/QE keys when the Right Mouse Button is held down and the Mouse is not moved
- Crash when calling default interface method from virtual method with same name
- [Android] Unity does not include the ".aab" extension for an AppBundle when it is built via script with the buildPlayerOptions.locationPathName = "AppName.apk" and EditorUserBuildSettings.buildAppBundle = true
shubear
Apr 19, 2021 06:36
Same issue on P31iCloudPlugin.bundle on 2020.3.4f1
joonturbo
Apr 16, 2021 12:48
encountering this issue with P31iCloudPlugin.bundle on 2020.3.2f1
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!
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
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).
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?
zingperformance
Mar 31, 2021 15:31
Is this problem fixed in Unity 2021.1.1f1??