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
Comments (1)
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
Gearme
Aug 14, 2017 03:59
Second. I get the same exception when trying to build new project (with a custom native plugin).