Search Issue Tracker
Fixed in 2017.2.0f3
Votes
0
Found in
2017.1.0a6
Issue ID
896128
Regression
Yes
Build & Run button does not build, throws an error
To reproduce:
1. Open a new project;
2. Press File > Build & Run (or Ctrl+B);
or
2. Press File > Build Settings... > Build & Run.
Expected result: if Build & Run or Ctrl+B is pressed, Editor builds the project.
Actual result: errors "UnityEditor.BuildPlayerWindow+BuildMethodException: Build location for buildTarget StandaloneWindows64is not valid"(2017.1.0b1) and "Couldn't call method BuildPlayerAndRun because the class BuildPlayerWindow or method couldn't be found."(2017.1.0a6) are thrown when Build & Run button is pressed. Editor does not build the project.
Reproduced on version: 2017.1.0a6, 2017.1.0b1.
Not reproduced on versions: 5.5.3f1, 5.6.0f3, 2017.1.0a5.
Regression found on: 2017.1.0a6.
Verified on version: 2017.1.0b6 (38ec4e48ade7).
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