Search Issue Tracker
Fixed in 2017.2.0f3
Votes
0
Found in
2017.1.0b1
Issue ID
899361
Regression
Yes
Build & run doesn't work if the project is built for the first time
Reproduction steps:
1. Create a new project
2. Press Build & run
3. Exception printed out:
UnityEditor.BuildPlayerWindow+BuildMethodException: Build location for buildTarget StandaloneWindows64is not valid.
at UnityEditor.BuildPlayerWindow+DefaultBuildMethods.GetBuildPlayerOptions (BuildPlayerOptions defaultBuildPlayerOptions) [0x001cd] in C:\buildslave\unity\build\Editor\Mono\BuildPlayerWindowBuildMethods.cs:224
at UnityEditor.BuildPlayerWindow.CallBuildMethods (BuildOptions defaultBuildOptions) [0x0002e] in C:\buildslave\unity\build\Editor\Mono\BuildPlayerWindowBuildMethods.cs:78
UnityEditor.HostView:OnGUI()
Expected: If project is built for the first time, Build & run should behave the same way as in earlier versions
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
- Warnings related to App Icon are being thrown when building project to VisionOS Platform
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
Gearme
Aug 14, 2017 03:59
Second. I get the same exception when trying to build new project (with a custom native plugin).