Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X
Votes
2
Found in
2017.4.3f1
2018.4.0f1
2019.2.0a1
2019.3.0a1
2020.1.0a1
Issue ID
1191481
Regression
Yes
[Build Callbacks] Build is not failing when BuildFailedException is thrown in the PostProcessScene Callback
How to reproduce:
1. Open the user attached "FailBuild" project
2. Build a project for any platform
Expected results: Build is failed when BuildFailedException is thrown
Actual results: Build is not failed when BuildFailedException is thrown
Reproducible with: 2017.4.3f1, 2017.4.33f1, 2018.4.11f1, 2019.2.10f1, 2019.3.0b7, 2020.1.0a9
Not reproducible with: 2017.4.2f2
Additional note: Build fails only when "Build and Run" is clicked instead of "Build"
Comments (5)
-
rajandeepavontus
Nov 17, 2020 18:21
It'll be nice to have this fixed. We have a PostProcess that was throwing a BuildFailedException but no one realized it because the build was passing.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2020.2):
Fixed with 2021.2.0a11, backported to 2020.3.8f1
Resolution Note (fix version 2021.1):
Fixed in 2021.1.6f1