Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2022.1.X
Votes
4
Found in
2022.1.0a6
2022.1.0b4
2022.2
Issue ID
1399524
Regression
Yes
[M1][WebGL] Editor throws errors when building for WebGL on native Apple Silicon Editor
Reproduction steps:
1. Open the user's project
2. Build for WebGL
Expected result: Build succeeds
Actual result: Build fails and throws errors
Reproducible with: 2022.1.0a6, 2022.1.0b6, 2022.2.0a3
Not reproducible with: 2021.2.11f1, 2022.1.0a5
Could not test with: 2019.4.35f1, 2020.3.27f1 (No Silicon Editor)
Errors:
Unhandled Exception:
System.TypeInitializationException: The type initializer for 'Sys' threw an exception. ---> System.DllNotFoundException: /Applications/Unity/2022.1.0a7_c277161121c6/Unity.app/Contents/MonoBleedingEdge/lib/../lib/libmono-native.dylib assembly:<unknown assembly> type:<unknown type> member:(null)
at (wrapper managed-to-native) Interop+Sys.LChflagsCanSetHiddenFlag()
at Interop+Sys..cctor () [0x00000] in <a7d051a418ca47de8168dbadc65f5694>:0
Comments (1)
-
nroth
Apr 15, 2022 03:51
I'm having the same exact issue, only on the latest macOS toolchain, with a different program. Mind sharing how you fixed this?
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
- Physics Used Memory keeps growing when GameObject colliders are enabled and disabled
- Errors are thrown and Inspector's UI element is not drawing when a GameObject with script component using a List<T> attached is selected
- ConfigurableJoint's parameters are not saved in the Prefab after Runtime Prefab baking
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
- Hidden Tabs do not shift into empty space after closing visible Tabs
Resolution Note (fix version 2022.2):
Fixed the root cause behind "The type initializer for 'Sys' threw an exception." when running the editor on Apple silicon devices.
Fixed in 2022.2.0a5
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0b10