Search Issue Tracker
Fixed in 1.0.0-preview1
Votes
0
Found in [Package]
0.9.6
Issue ID
1178792
Regression
No
"Destroy can only be called from the main thread" is thrown after building a IL2CPP standalone and Input System pacakge
How to reproduce:
1. Make sure that IL2CPP is installed
2. Open attached project "BugReproduction.zip"
3. In Editor, click on Window -> General -> TestRunner -> PlayMode -> "Run all in player (Standalone Windows64)"
4. Observe the built standalone
Expected result: no errors are thrown
Actual result: "UnityException: Destroy can only be called from the main thread." is thrown
Reproducible with: 2019.2.7f2(0.9.6), 2019.3.0b4(0.9.6), 2020.1.0a4(0.9.6)
Could not test with: 2017.4 due to IL2CPP errors, 2018.4 due to multiple package errors
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Inconsistent behaviour when interacting with different dropdown types with pointer events on parent Visual Element
- Hidden GameObjects won't re-enable when they have call "DontDestroyOnLoad" function
- Overlay Canvas are rendered on each split-screen camera when HDR is enabled
- [Android] The Player loses focus when using UnityEngine.Handheld.StartActivityIndicator() with Facebook SDK
- Build fails with "Building Library/Bee/artifacts/MacStandalonePlayerBuildProgram/gahcy/hj9mx3z/951.0 failed with output:..." errors when Scripting Backend is set to IL2CPP
Add comment