Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
1
Found in
2021.3.11f1
2022.1.19f1
2022.2.0b10
2023.1.0a13
2023.2.0a1
2023.3.0a3
Issue ID
UUM-16389
Regression
No
Build crash when loading next scene with ScriptableObject that has UNITY_EDITOR only fields in a generic class.
Reproduction steps:
1. Open the attached user’s project
2. Click Edit > Build And Run
3. In Build, click the “Load Next Scene (Crash)” Button
Expected result: Player build loads the next scene, just as in Editor Play Mode
Actual result: Player build crashes
Reproducible with: 2021.2.0a18, 2021.3.11f1, 2022.1.19f1, 2022.2.0b10, 2023.1.0a13
Couldn’t test with: 2020.3.40f1, 2021.1.28f1 (couldn’t build because the list of \[SerializeReference] objects being deserialized is from a more recent version of Unity), 2021.2.0a1, 2021.2.0a17 (couldn’t test because ‘AssetDatabase’ does not contain a definition for 'SaveAssetIfDirty)
Reproducible on: Windows 11 Pro 21H2, Ubuntu 20.04.5
Note: In Player.log, there is an error saying that “sharedassets1.asset” is corrupted
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
- 2D Freeform Light shadows disappear when light center is offset from shape bounds
- Crash on MarkAllDependencies when opening scenes with Assets from the YarnSpinner package
- Crash on CollectAllSceneManagerAndObjectIDs when opening a specific Scene
- GPU device suspended error when replaying a video in the Video Player with NVIDIA Vertical Sync set to Fast
- GPU device suspended error when replaying a video in the Video Player with NVIDIA Vertical Sync set to Fast
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. The user has found an acceptable workaround some time ago.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (2023.3.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. The user has found an acceptable workaround some time ago.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.