Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2021.2.X
Votes
0
Found in
2021.2.0a9
Issue ID
1348307
Regression
Yes
Non-development macOS Standalone builds with IL2CPP scripting backend have invalid signature, causing them not to run
Running a Universal binary on Apple silicon (M1) hardware fails with EXC_BAD_ACCESS (Code Signature Invalid)
Repro:
1) On an Intel or Apple silicon mac, build a Universal binary with an IL2CPP backend.
2) Run on an Intel machine and an Apple silicon machine
Result:
The build runs on the Intel machine, but crashes with EXC_BAD_ACCESS (Code Signature Invalid) on an Apple Silicon machine
Expected:
No crash.
Tested on: 2021.2.0b2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UnityYamlMerge.exe doesn't correctly handle merge conflicts in modified properties on a prefab variant
- Inconsistent color scheme in "Details" section of "Select Presets" inspector window
- Crash on __pthread_kill when launching Editor via command-line with "-disableManagedDebugger" argument
- [VFX] Deleting “New Group Node” name doesn’t allow to type or add new name
- [VFX] Creating a long Group Node name breaks nodes boarders
Add comment