Search Issue Tracker
Duplicate
Votes
0
Found in
2017.1.0b4
Issue ID
909485
Regression
Yes
Using ⌘+B or CTRL+B to open Build Settings window results in an error on newly created projects
Steps to reproduce:
1) Create a new project (important).
2) When the project is open in Unity, press ⌘+B on Mac or CTRL+B on Windows.
An error appears in the Console:
UnityEditor.BuildPlayerWindow+BuildMethodException: Build location for buildTarget StandaloneOSXIntel64is not valid.
at UnityEditor.BuildPlayerWindow+DefaultBuildMethods.GetBuildPlayerOptions (BuildPlayerOptions defaultBuildPlayerOptions) [0x001cd] in /Users/builduser/buildslave/unity/build/Editor/Mono/BuildPlayerWindowBuildMethods.cs:224
at UnityEditor.BuildPlayerWindow.CallBuildMethods (BuildOptions defaultBuildOptions) [0x0002e] in /Users/builduser/buildslave/unity/build/Editor/Mono/BuildPlayerWindowBuildMethods.cs:78
UnityEditor.BuildPlayerWindow:BuildPlayerAndRun()
The Build Settings window can still be opened using ⌘+Shift+B or CTRL+Shift+B or via menu bar.
After this is done, ⌘+B and CTRL+B starts working as well.
If the project is closed and reopening, the bug disappears.
Expected result: Build Settings window pops up.
Actual result: Error appears; the build window doesn't appear.
This happens on both macOS and Windows with all platforms selected (iOS, Android, Standalone).
Reproduced on:
2017.1.0b4, 2017.1.0b1, 2017.1.0a6
Did not reproduce:
2017.1.0a5
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Code runs slower when using a cached exception instance compared to creating a new one
- Broken UI in Default Preset Add Section of "Preset Manager" window
- [iOS] The Player freezes when closing the Notification Center and quickly swiping down from top
- Crash on Texture2D:SetPixelImpl when rapidly calling Texture2D.Apply()
- Graph Lines are not rendered when using Experimental GraphView or GridBackground
Add comment