Search Issue Tracker
Fixed in 2021.1.X
Votes
1
Found in
2020.1
2020.2
2020.2.0b1
Issue ID
1276232
Regression
No
Linux player builds with Mono scripting backend fails with a confusing error message if only IL2CPP players are installed
Reproduction steps:
1. Download Unity with only Linux Build Support (IL2CPP)
2. Create a new project or open an existing one
3. Open Player Settings (Edit - > Project Settings -> Player)
4. Set Scripting Backend to Mono
5. Open Build Settings (File -> Build Settings)
6. Set Target Platform to Linux and enable Development Build
7. Build the project
Expected result: Build fails with a message indicating that Mono Scripting Backend is missing
Actual result: Build fails with a message indicating that moving temporary files failed
Reproduces on: 2020.1.5f1, 2020.2.0b2
Reproduces on Mac and Windows Editors
Error message:
IOException: Failed to Move File / Directory from 'Temp/StagingArea\LinuxPlayer' to 'Temp/StagingArea\build.x86_64'.
UnityEditor.FileUtil.MoveFileOrDirectory (System.String source, System.String dest) (at <3d7c86b365634083bceadac5c7f36490>:0)
UnityEditor.LinuxStandalone.LinuxDesktopStandalonePostProcessor.RenameStagingAreaFile (UnityEditor.Modules.BuildPostProcessArgs args, System.String from, System.String to) (at /home/bokken/buildslave/unity/build/PlatformDependent/LinuxStandalone/Extensions/Managed/LinuxDesktopStandalonePostProcessor.cs:80)
UnityEditor.LinuxStandalone.LinuxDesktopStandalonePostProcessor.RenameFilesInStagingArea (UnityEditor.Modules.BuildPostProcessArgs args) (at /home/bokken/buildslave/unity/build/PlatformDependent/LinuxStandalone/Extensions/Managed/LinuxDesktopStandalonePostProcessor.cs:65)
DesktopStandalonePostProcessor.SetupStagingArea (UnityEditor.Modules.BuildPostProcessArgs args, System.Collections.Generic.HashSet`1[T] filesToNotOverwrite) (at <3d7c86b365634083bceadac5c7f36490>:0)
DesktopStandalonePostProcessor.PostProcess (UnityEditor.Modules.BuildPostProcessArgs args) (at <3d7c86b365634083bceadac5c7f36490>:0)
Rethrow as BuildFailedException: Exception of type 'UnityEditor.Build.BuildFailedException' was thrown.
DesktopStandalonePostProcessor.PostProcess (UnityEditor.Modules.BuildPostProcessArgs args) (at <3d7c86b365634083bceadac5c7f36490>:0)
UnityEditor.Modules.DefaultBuildPostprocessor.PostProcess (UnityEditor.Modules.BuildPostProcessArgs args, UnityEditor.BuildProperties& outProperties) (at <3d7c86b365634083bceadac5c7f36490>:0)
UnityEditor.PostprocessBuildPlayer.Postprocess (UnityEditor.BuildTargetGroup targetGroup, UnityEditor.BuildTarget target, System.String installPath, System.String companyName, System.String productName, System.Int32 width, System.Int32 height, UnityEditor.BuildOptions options, UnityEditor.RuntimeClassRegistry usedClassRegistry, UnityEditor.Build.Reporting.BuildReport report) (at <3d7c86b365634083bceadac5c7f36490>:0)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr, Boolean&)
Notes:
A pop-up window with the first line of the error message appears when build fails as well.
Linux Build Support (IL2CPP) is not available on Unity 2019.4, therefore the issue is not reproducible
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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
nching_unity
Sep 26, 2024 17:32
is there a workaround if we cannot update to 2021.1.X?