Search Issue Tracker
Duplicate
Votes
0
Found in
2019.3.0a6
2019.3.0b7
2020.1.0a1
Issue ID
1192080
Regression
Yes
[SerializeField] Build fails with errors when using a serialized field defined in a custom dll file
How to reproduce:
1. Open the user attached "2019.3 - Test" project
2. Build this project
3. If no error, Build again, the error should pop up
(Build or Build and Run doesn't matter)
Expected results: Build is successful
Actual results: Build fails if it previously succeeded. If it previously succeeded it will fail, etc.
Reproducible with: 2019.3.0a6, 2019.3.0b7, 2020.1.0a1
Not reproducible with: 2017.4.33f1, 2018.4.11f1, 2019.2.10f1, 2019.3.0a5
Additional notes:
1. On Unity versions from 2019.3.0a1 to 2019.3.0a5 compilation errors are thrown:
"ArgumentException: The Assembly UnityEngine.UI is referenced by X. But the dll is not allowed to be included or could not be found."
2. The build may succeed when only building, and fail when issuing "Build and run", and vice versa
3. The issue is not reproducible on 2020.1.0a2
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
This is a duplicate of issue #1169148