Search Issue Tracker
Fixed in 5.5.0
Votes
1
Found in
5.3.4p1
Issue ID
782543
Regression
No
Editor doesn't stop player build if scripts have compilation errors in the editor
This causes editor to be unable to serialize data for scripts, since it has no assemblies to scan for serializable fields. However, building the player succeeds, and it will then try to deserialize fields on startup. Since there's no data we crash with error messages in the log:
The file 'D:/Projects/UnityProjects/New Unity Project 488/bin/b_Data/level0' is corrupted! Remove it and launch unity again!
[Position out of bounds!]
(Filename: Line: 217)
The file 'D:/Projects/UnityProjects/New Unity Project 488/bin/b_Data/level0' is corrupted! Remove it and launch unity again!
[Position out of bounds!]
(Filename: Line: 223)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment