Search Issue Tracker
Won't Fix
Votes
0
Found in
5.6.1p2
Issue ID
921524
Regression
Yes
"Build" vs "Build and Run" has different outcomes
Repro steps:
1. Open "ReproProject" project
2. Build for Windows Standalone through the build settings
3. See that the project finishes building (with some errors)
4. Restart Unity
5. Build the project by "Build and Run"
Expected result: The project should build exactly as the one with the "Build" Option
Actual result: The building of the project fails with errors ("Error building Player: 2 errors")
Reproduced with: 2017.2.0b1, 2017.1.0f1, 5.6.2f1, 5.5.3p4, 5.5.3p3
Regression introduced in: 5.5.3p3
Did not reproduce on: 5.5.0f3, 5.5.2p3, 5.5.3f1, 5.5.3p1, 5.5.3p2,
Note:
If you first build the project with the "Build" option and, without restarting Unity, you build with "Build and Run" the errors don't appear and the build finishes successfully
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
Add comment