Search Issue Tracker
Duplicate
Votes
0
Found in [Package]
1.6.0
Issue ID
1362245
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
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
- Motion Vector texture reports incorrect Mesh data when Mesh is coming from off-screen
This is a duplicate of issue #962800