Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.6.0
Issue ID
BUR-1415
Regression
Yes
UnityException is thrown in Build when using Burst Direct Call methods
How to reproduce:
1. Open the attached project (burst-error2.zip)
2. Open scene Scenes/SampleScene
3. Go to File -> Build Settings
4. Enable the "Development Build" setting and click "Add Open Scenes"
5. Build and Run the project
6. Observe the Build
Expected result: no errors are thrown in the Build
Actual result: "UnityException: CompileAsyncDelegateMethod can only be called from the main thread" is thrown in the Build
Reproducible with: 1.6.0-pre.4, 1.6.0 (2021.1.0b10, 2021.1.22f1)
Not reproducible with: 1.6.0-pre.4, 1.6.0 (2020.3.19f1)
Could not test with: 2019.4.30f1, 2021.1.0a1, 2021.1.0b9, 2021.2.0b13, 2022.1.0a10 (cannot resolve compiler errors)
Notes:
1. No errors are thrown in the Editor
2. The project fails to build on Mac ("invalid macOS bundle <...>")
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
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
- Scene view has Y coordinates of the Screen Position node flipped when some of the URP features are disabled
- Volumetric fog shader variants are missing from build when "Strict Shader Variant Matching" is disabled
- Unnecessary modifications clutter the Scene when using a RectTransform driven by a LayoutGroup in a Prefab
Resolution Note:
From https://unity.slack.com/archives/C0105CH72UV/p1659620189235489?thread_ts=1656520443.840829&cid=C0105CH72UV, it seems it has already be fixed and should be closed. See https://issuetracker.unity3d.com/issues/runtimeinitializeonloadmethod-is-not-called-if-it-is-part-of-nested-class