Search Issue Tracker
Fixed in Unity 2017.3.0f3
Votes
1
Found in
2017.1.0b4
Issue ID
909650
Regression
Yes
Editor offers previous project's build path as build destination
-e: see title, it used to start with the current project's main folder
--regression from 2017.1b3
-repro:
--create new project "01"
--make a standalone build into "01/builds"
--create new project "02"
--try making new build
--NOTICE it offers you to build 02 into "01/builds"
Note: Sometimes it points to project/assets folder causing a failure in build and throwing this error (which is expected). Make sure to select a correct/valid build path
UnityEditor.BuildPlayerWindow+BuildMethodException: Build failed with errors.
at UnityEditor.BuildPlayerWindow+DefaultBuildMethods.BuildPlayer (BuildPlayerOptions options) [0x001b9] in C:\buildslave\unity\build\Editor\Mono\BuildPlayerWindowBuildMethods.cs:162
at UnityEditor.BuildPlayerWindow.CallBuildMethods (Boolean askForBuildLocation, BuildOptions defaultBuildOptions) [0x00050] in C:\buildslave\unity\build\Editor\Mono\BuildPlayerWindowBuildMethods.cs:83
UnityEditor.HostView:OnGUI()
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
- [Presets] DefaultInpector type needs to be blacklisted
- Default Inspector Header is shown when double clicking on a scene
- [LWRP] Base map is missing on some materials after upgrading LWRP package
- Metal error when using subsurface scattering in HDRP
- gameObject.SendMessage doesn't accept value as a function argument correctly in the .NET 4.x Scripting Runtime
raptorpos
Aug 04, 2017 02:51
Yes. I face this also. I used Unity 2017.1.0f3
Filipp_Kuzmenko
Jul 15, 2017 07:59
Got this with Unity 2017.1.0f1(After updating from Unity 5.6.x) & Unity 2017.1.0f3