MacOS and project with symlinks

Unity Engine
1

When developing multiplayer games I’ve used symlinks with great success on both MacOS and Windows.
With 2018.3 I’m getting errors on MacOS (still works on the Windows version) like

error CS2011: Unable to open response file: Temp/UnityTempFile-b22c873c7ae094d91b6cd65ce970e2f4

or

MissingMethodException: void UnityEditor.Scripting.Compilers.ScriptCompilerBase.RunAPIUpdaterIfRequired(string)
UnityEditor.Scripting.Compilers.ScriptCompilerBase.BeginCompiling () (at /Users/builduser/buildslave/unity/build/Editor/Mono/Scripting/Compilers/ScriptCompilerBase.cs:65)
UnityEditor.Scripting.ScriptCompilation.CompilationTask.QueuePendingAssemblies () (at /Users/builduser/buildslave/unity/build/Editor/Mono/Scripting/ScriptCompilation/CompilationTask.cs:236)
UnityEditor.Scripting.ScriptCompilation.CompilationTask.Poll () (at /Users/builduser/buildslave/unity/build/Editor/Mono/Scripting/ScriptCompilation/CompilationTask.cs:143)
UnityEditor.Scripting.ScriptCompilation.EditorCompilation.CompileScriptAssemblies (UnityEditor.Scripting.ScriptCompilation.ScriptAssembly[] scriptAssemblies, UnityEditor.Scripting.ScriptCompilation.ScriptAssemblySettings scriptAssemblySettings, System.String tempBuildDirectory, UnityEditor.Scripting.ScriptCompilation.EditorScriptCompilationOptions options, UnityEditor.Scripting.ScriptCompilation.CompilationTaskOptions compilationTaskOptions, UnityEditor.Scripting.ScriptCompilation.EditorCompilation+CompileScriptAssembliesOptions compileScriptAssembliesOptions) (at /Users/builduser/buildslave/unity/build/Editor/Mono/Scripting/ScriptCompilation/EditorCompilation.cs:1053)
UnityEditor.Scripting.ScriptCompilation.EditorCompilation.CompileCustomScriptAssemblies (UnityEditor.Scripting.ScriptCompilation.ScriptAssemblySettings scriptAssemblySettings, System.String tempBuildDirectory, UnityEditor.Scripting.ScriptCompilation.EditorScriptCompilationOptions options, UnityEditor.BuildTargetGroup platformGroup, UnityEditor.BuildTarget platform) (at /Users/builduser/buildslave/unity/build/Editor/Mono/Scripting/ScriptCompilation/EditorCompilation.cs:965)
UnityEditor.Scripting.ScriptCompilation.EditorCompilation.CompileCustomScriptAssemblies (UnityEditor.Scripting.ScriptCompilation.EditorScriptCompilationOptions options, UnityEditor.BuildTargetGroup platformGroup, UnityEditor.BuildTarget platform) (at /Users/builduser/buildslave/unity/build/Editor/Mono/Scripting/ScriptCompilation/EditorCompilation.cs:959)
UnityEditor.Scripting.ScriptCompilation.EditorCompilationInterface+<CompileCustomScriptAssemblies>c__AnonStorey3.<>m__0 () (at /Users/builduser/buildslave/unity/build/Editor/Mono/Scripting/ScriptCompilation/EditorCompilationInterface.cs:259)
UnityEditor.Scripting.ScriptCompilation.EditorCompilationInterface.EmitExceptionAsError[T] (System.Func`1[TResult] func, T returnValue) (at /Users/builduser/buildslave/unity/build/Editor/Mono/Scripting/ScriptCompilation/EditorCompilationInterface.cs:97)
UnityEditor.Scripting.ScriptCompilation.EditorCompilationInterface:CompileCustomScriptAssemblies(EditorScriptCompilationOptions, BuildTargetGroup, BuildTarget)

Since having two editors running for multiplayer development greatly speeds up the work flow I’d really like to get it working again somehow!

2

Could you please submit a bug report with a minimal reproduction project for this issue and reply in here with the issue ID?

3

I tried creating a new project and it worked. I’m not sure what the problem is with my current project since the Windows version works fine but it fails on MacOS.

Could it be a permission issue when Unity creates the temp/ folder?

4

Have you looked at this?

5

Yes thanks, if you’re referring to the “hardlink” method it turns out it hasn’t been supported in MacOS for quite some time.

I think I’ll just avoid working on MacOS for now and then see what happens when 2018.3 final is out.

6

We actually have a bug logged about this that could be related. I’ll try to get it public and will post an update here once I know more. Stay tuned.

1 Like
7

Thanks for your time!

1 Like
8

So it looks like the report we have logged for this is exclusive to 2019.1 because we weren’t able to reproduce the problem in 2018.3. Is there a chance you could provide us with your project and a bug report?

9

Sorry for the late reply. I was about to create a bug report but when I opened the project in 2018.3.0b6 it seemed to work again?

I had a few cloned projects where I would get the error and they all seem to work again.

I didn’t change anything so either the upgrade process or an actual fix corrected this.

Thanks for that.

1 Like