Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2021.2.X, 2022.1.X
Votes
0
Found in
2021.2.17f1
2022.1
Issue ID
1412356
Regression
Yes
BuildFailedException is thrown when building a new project
Steps to reproduce:
1. Open the attached project
2. Press File > Build and Run
Expected result: Project is built
Actual result: Build fails on BuildFailedException: Incremental Player build failed
Reproducible with: 2021.2.17f1, 2022.1.0b13,
Not reproducible with: 2019.4.37f1, 2020.3.31f1, 2021.2.16f1, 2022.2.0a1, 2022.2.0a8
Notes:
-seems to only reproduce on Windows
-reproduced with Windows Standalone and with WebGL
-only reproduces when the Project and the Editor are located in different partitions
Workaround:
-Move the Project to the same partition as the Editor
Comments (1)
-
Su-35FlankerE
May 16, 2023 12:48
How exactly do I move the project to the same file location as Unity Editor?
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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a1
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0b14
Resolution Note (fix version 2021.2):
Fixed in 2021.2.17f1