Search Issue Tracker
Not Reproducible
Votes
29
Found in
2017.1.0b4
Issue ID
909581
Regression
Yes
Building on top of old build while its output_log.txt is open causes build to fail
Steps to reproduce:
1. Create new project
2. Build and run
3. Once resolution selection screen launches - close it
4. Navigate to _data folder located in same folder as build executable
5. open output_log.txt
6. Return to editor and do build and run to overwrite previous build
7. Build fails. Contents of previous build are deleted (.exe and all items that were in _data folder)
Not reproducible: 5.4.5p2
Reproduced with:
5.5.0f3 (has somewhat useful error: OperationCanceledException: Failed to prepare target build directory. Is a built game instance running?)
5.5.3p3 (no warning or error)
5.6.1f1 (no warning or error)
2017.1.0b4 (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 )
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
- Inspector's custom tooltip is displayed incorrectly when the name is truncated in UI toolkit
- Crash on ScriptableRenderLoopDraw when rendering a specific VFX in Play Mode
- The script is not renamed in the Project window when renaming and a compilation Error is present
- Average FPS in Play Mode degradation on a newly created BiRP project when it's upgraded from 2020.3.48f1 to a newer Editor version
- DecoratorDrawer indentation is incorrect when it is called with EditorGUI
YaroslavSm
Aug 07, 2020 18:58
Reproducible. Just close an old application.
unity_kD8okEN-apXI1A
Feb 15, 2020 06:54
Yes I got it!! I just delete the previous build and extra Components like probuilder and then build and it works for me .
benedictrasmussen
Feb 04, 2018 16:24
I was having this issue due to an upgrade recently. I had been using 2017.1.0f1 and upgraded to 2017.3.0f3. I did not uninstall 0f1, and found that depending on which shiortcut I used to open Unity I was opening different versions. The older version (0f1) was causing the issue for me. 0f3 appears to work fine.
Personally I simply deleted the old version. No reason to keep two confusing versions around.
Ankshil
Feb 02, 2018 13:00
Build completed with a result of 'Failed'
UnityEngine.GUIUtility: processEvent(Int32, IntPtr)
UnityEditor.BuildPlayerWindow+BuildMethodException: 2 errors
at UnityEditor.BuildPlayerWindow+DefaultBuildMethods.BuildPlayer (BuildPlayerOptions options) [0x00207] in /Users/builduser/buildslave/unity/build/Editor/Mono/BuildPlayerWindowBuildMethods.cs:172
at UnityEditor.BuildPlayerWindow.CallBuildMethods (Boolean askForBuildLocation, BuildOptions defaultBuildOptions) [0x00050] in /Users/builduser/buildslave/unity/build/Editor/Mono/BuildPlayerWindowBuildMethods.cs:83
UnityEngine.GUIUtility: processEvent(Int32, IntPtr)
------------------------------------------------------------------------------------------------------------------------
I had the same problem when I tried to build an app. I was using unity 2017.2.1f1
I solved the problem by changing the tools in the sdk folder with the tools_r25.2.5
Download this file online here - https://androidsdkoffline.blogspot.in/p/android-sdk-tools.html
First just rename the tools folder already present in sdk root folder with toolsXXXX and then
Unzip tools_r25.2.5 and copy its tools into the sdk root folder.
Still, the error was there then I realised that the jdk version is not correct too. so download jd1.8 here - http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
Download java kit 8u161 and then in Edit->Preferences ->External Tools
Set these jdk1.8 path and sdk path
It worked for me after that and I built my first app using Unity 3d
I hope it works for you too.
anyadahalor
Nov 20, 2017 13:54
For anyone still struggling with this issue (I was), here is a possible solution.
I had the problem when I changed version number in player settings. I reverted it and still didn't work.
I saved both the scene and the project and it worked. So try saving the project and the scene (even if you closed unity before... I have done that, deleted .vs folder, to no avail)
PucaPuca
Nov 14, 2017 04:01
LegalSin's fix below (aug17) worked for me. VisualStudio hidden folder (.vs) and project files causing conflicts. The build flowed correctly after I removed those.
CjaywesTT
Nov 09, 2017 09:45
Is this fixed at all? Saying no voting due to it being solved, what's the solution? I seen somewhere someone hit reimport all assets and it worked for them but it just doesn't seem to be fix for something totally different. Went through all of Unity 2017's player options and didn't see anything out of the ordinary.
alecsis
Oct 31, 2017 21:05
Hey guys, I had the same error, my problem was because I tried to make the android build inside the assets folder of the project. When I changed the folder path for the build it worked. Hope it helps you.
claudioal
Sep 25, 2017 15:09
It deletes the temp folders, uninstalls Unity, deletes the Unity folders that are inside the hidden "AppData" folder and reinstalls Unity ...
dcolwell634
Aug 25, 2017 13:50
Hey Guys,
I was working with HoloLens and tried reinstalling Unity as a troubleshooting step. Upon reinstall, I was getting this error when doing a build. I changed the Scripting Backend to .NET in the Player/Other Settings section and this fixed it. Based on my own research I can only assume the other version (IL2CPP) was missing some dll's. I was getting another error in conjunction with this one, saying something about could not find analyitcs.dll. Either way, give this a shot guys. Maybe it will work for you too.