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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment