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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Add comment