Unable to find player assembly BURST AOT Compiler

Unable to find player assembly: /Users/name/UNITY/ProtoGame/Temp/StagingArea/Data/Managed/UnityEngine.TestRunner.dll
UnityEngine.Debug:LogWarning(Object)
Unity.Burst.Editor.BurstAotCompiler:OnPostBuildPlayerScriptDLLsImpl(BuildReport) (at Library/PackageCache/com.unity.burst@1.2.3/Editor/BurstAotCompiler.cs:212)
Unity.Burst.Editor.BurstAotCompiler:OnPostBuildPlayerScriptDLLs(BuildReport) (at Library/PackageCache/com.unity.burst@1.2.3/Editor/BurstAotCompiler.cs:90)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr) (at /Users/builduser/buildslave/unity/build/Modules/IMGUI/GUIUtility.cs:197)

Using:
-macOS catalina 10.15.5
-Unity 2019.4.4f1
-Burst 1.2.3

When building for IOS platform Unity throws me this warning. I disabled Burst compilation in (Project settings > Burst AOT Settings) and the warning was gone but I’m afraid that this also disables burst in my build. I want to be able to fix this problem without disabling Burst AOT compiler.

Hi - thanks for reporting this. As you noted, it is “just” a warning, and you can safely ignore this one, annoying as it may be.

A fix for this bug will be in the next 2020.2 alpha release, but for previous Unity versions, the workaround is simply to ignore the warning. Unless you have warnings-as-errors enabled… in which case it’s more problematic. You would need to disable warnings-as-errors while doing player builds.

Even with the error present, is the Burst compilation enabled in my build?

Bump, any reply about this question?

Hi… can i get some help please… https://discussions.unity.com/t/801715

Hi, I am also getting this log warning but it is failing compilation. Is this a warnings-as-errors issue? How can I disable warnings-as-errors if so?

Unable to find player assembly: /content/svo-games/Project/Temp/StagingArea/Data/Managed/UnityEngine.TestRunner.dll
UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
UnityEngine.DebugLogHandler:LogFormat(LogType, Object, String, Object[])
UnityEngine.Logger:Log(LogType, Object)
UnityEngine.Debug:LogWarning(Object)
Unity.Burst.Editor.BurstAotCompiler:OnPostBuildPlayerScriptDLLsImpl(BuildReport) (at Library/PackageCache/com.unity.burst@1.2.3/Editor/BurstAotCompiler.cs:212)
Unity.Burst.Editor.BurstAotCompiler:OnPostBuildPlayerScriptDLLs(BuildReport) (at Library/PackageCache/com.unity.burst@1.2.3/Editor/BurstAotCompiler.cs:90)
UnityEditor.Build.BuildPipelineInterfaces:OnPostBuildPlayerScriptDLLs(BuildReport) (at /home/builduser/buildslave/unity/build/Editor/Mono/BuildPipeline/BuildPipelineInterfaces.cs:487)
(Filename: Library/PackageCache/com.unity.burst@1.2.3/Editor/BurstAotCompiler.cs Line: 212)

/content/svo-games/Project/Library/PackageCache/com.unity.burst@1.2.3/.Runtime/bcl.exe exited after 3385 ms.
/usr/bin/ld: /usr/lib/llvm-6.0/bin/../lib/LLVMgold.so: error loading plugin: /usr/lib/llvm-6.0/bin/../lib/LLVMgold.so: cannot open shared object file: No such file or directory
(Filename: unknown Line: 0)

clang: error: linker command failed with exit code 1 (use -v to see invocation)
(Filename: unknown Line: 0)

BuildFailedException: Burst compiler (1.2.3) failed running

stdout:
The native link step failed. Check previous exception in the log - linker command line : "/usr/bin/clang "@/tmp/tmp30e5e4dd.tmp""
stderr:
/usr/bin/ld: /usr/lib/llvm-6.0/bin/../lib/LLVMgold.so: error loading plugin: /usr/lib/llvm-6.0/bin/../lib/LLVMgold.so: cannot open shared object file: No such file or directory
clang: error: linker command failed with exit code 1 (use -v to see invocation)

  at Unity.Burst.Editor.BurstAotCompiler+BclRunner.RunProgram (UnityEditor.Utils.Program p, System.String exe, System.String args, System.String workingDirectory, UnityEditor.Scripting.Compilers.CompilerOutputParserBase parser, UnityEditor.Build.Reporting.BuildReport report) [0x001f4] in /content/svo-games/Project/Library/PackageCache/com.unity.burst@1.2.3/Editor/BurstAotCompiler.cs:752
  at Unity.Burst.Editor.BurstAotCompiler+BclRunner.RunManagedProgram (System.String exe, System.String args, System.String workingDirectory, UnityEditor.Scripting.Compilers.CompilerOutputParserBase parser, UnityEditor.Build.Reporting.BuildReport report) [0x0004d] in /content/svo-games/Project/Library/PackageCache/com.unity.burst@1.2.3/Editor/BurstAotCompiler.cs:690
  at Unity.Burst.Editor.BurstAotCompiler+BclRunner.RunManagedProgram (System.String exe, System.String args, UnityEditor.Scripting.Compilers.CompilerOutputParserBase parser, UnityEditor.Build.Reporting.BuildReport report) [0x00001] in /content/svo-games/Project/Library/PackageCache/com.unity.burst@1.2.3/Editor/BurstAotCompiler.cs:664
  at Unity.Burst.Editor.BurstAotCompiler.OnPostBuildPlayerScriptDLLsImpl (UnityEditor.Build.Reporting.BuildReport report) [0x0070f] in /content/svo-games/Project/Library/PackageCache/com.unity.burst@1.2.3/Editor/BurstAotCompiler.cs:332
  at Unity.Burst.Editor.BurstAotCompiler.OnPostBuildPlayerScriptDLLs (UnityEditor.Build.Reporting.BuildReport report) [0x0000e] in /content/svo-games/Project/Library/PackageCache/com.unity.burst@1.2.3/Editor/BurstAotCompiler.cs:90
  at UnityEditor.Build.BuildPipelineInterfaces.OnPostBuildPlayerScriptDLLs (UnityEditor.Build.Reporting.BuildReport report) [0x00033] in /home/builduser/buildslave/unity/build/Editor/Mono/BuildPipeline/BuildPipelineInterfaces.cs:487
UnityEngine.DebugLogHandler:Internal_LogException(Exception, Object)
UnityEngine.DebugLogHandler:LogException(Exception, Object)
UnityEngine.Logger:LogException(Exception, Object)
UnityEngine.Debug:LogException(Exception)
UnityEditor.Build.BuildPipelineInterfaces:OnPostBuildPlayerScriptDLLs(BuildReport) (at /home/builduser/buildslave/unity/build/Editor/Mono/BuildPipeline/BuildPipelineInterfaces.cs:491)
(Filename: Library/PackageCache/com.unity.burst@1.2.3/Editor/BurstAotCompiler.cs Line: 752)

Error building Player: 3 errors

Do we have an ETA for the fix and the dates for backport? Thanks

1 Like

Sorry, I missed this. Yes, as long as you’ve enabled Burst compilation, and assuming there are no errors (only warnings), then yes, Burst compilation will have been successful. You can double-check this by looking in your player build folder, for a file named lib_burst_generated.dll in a folder similar to ProjectName_Data\Plugins\x86_64.

The fix for this will be in 2020.2.0a21, which hasn’t yet been been released, but will be soon. The fix has been backported to 2019.4 and is available in 2019.4.7, which has been released.

Note that in addition to one of those Unity versions, you will also need to update your com.unity.test-framework package reference to 1.1.16.

@ek578 the actual error there is hiding under the warning:

/content/svo-games/Project/Library/PackageCache/com.unity.burst@1.2.3/.Runtime/bcl.exe exited after 3385 ms.
/usr/bin/ld: /usr/lib/llvm-6.0/bin/../lib/LLVMgold.so: error loading plugin: /usr/lib/llvm-6.0/bin/../lib/LLVMgold.so: cannot open shared object file: No such file or directory
(Filename: unknown Line: 0)
clang: error: linker command failed with exit code 1 (use -v to see invocation)
(Filename: unknown Line: 0)

Please could you try updating Burst from 1.2.3 to 1.3.4, and see if you still get this error?

Hi… I don’t want to hijack the thread … I was pointed here by simonbz.

I am running 2020.1.3 (was running 2020.1.2f1) on Mac. I have installed Animation Rigging 0.3.4 Preview package.

I have read that Animation Rigging requires:
2020.1 and later with .Net 4.x scripting runtime

I was following one of Valems YouTube videos where he installed Animation Rigging and after installing it I couldn’t Build the APK without this error.

Unable to find player assembly: /Users/jasonrooth/Documents/Unity/FP Newton VR/Temp/StagingArea/Data/Managed/UnityEngine.TestRunner.dll
UnityEngine.Debug:LogWarning(Object)
Unity.Burst.Editor.BurstAotCompiler:OnPostBuildPlayerScriptDLLsImpl(BuildReport) (at Library/PackageCache/com.unity.burst@1.2.0-preview.12/Editor/BurstAotCompiler.cs:212)
Unity.Burst.Editor.BurstAotCompiler:OnPostBuildPlayerScriptDLLs(BuildReport) (at Library/PackageCache/com.unity.burst@1.2.0-preview.12/Editor/BurstAotCompiler.cs:90)
UnityEditor.BuildPlayerWindow:BuildPlayerAndRun() (at /Users/builduser/buildslave/unity/build/Editor/Mono/BuildPlayerWindow.cs:124)

Since being made aware of this thread I have upgraded Burst to 1.4.0-preview4 and now have the following error:

Unable to find player assembly: /Users/jasonrooth/Documents/Unity/FP Newton VR/Temp/StagingArea/Data/Managed/UnityEngine.TestRunner.dll
UnityEngine.Debug:LogWarning(Object)
Unity.Burst.Editor.BurstAotCompiler:OnPostBuildPlayerScriptDLLsImpl(BuildReport) (at Library/PackageCache/com.unity.burst@1.4.0-preview.4/Editor/BurstAotCompiler.cs:287)
Unity.Burst.Editor.BurstAotCompiler:OnPostBuildPlayerScriptDLLs(BuildReport) (at Library/PackageCache/com.unity.burst@1.4.0-preview.4/Editor/BurstAotCompiler.cs:164)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr, Boolean&) (at /Users/builduser/buildslave/unity/build/Modules/IMGUI/GUIUtility.cs:189)

Let me know if it’s ok for me to continue to be apart of this thread or not.

bump

Hi @JRooth - yes, this is the right thread :slight_smile:

I just want to clarify first that what you posted are warnings, not errors. You can ignore them and still build a player successfully - unless there are any actual errors also occurring?

To get rid of the warnings, you can use either Unity 2019.4.7 or Unity 2020.2.0a21 (or newer).

Sorry for the bump.

Should I worry if I have these warnings in Unity 2019.4.23 , at the end of every build?

6979394--823304--build warning.png

(Edit: also with Burst 1.4.6)

I’m getting the same two warnings on Unity 2020.3.1f1 LTS using Burst 1.4.6

1 Like

Also happening for me in Unity 2021.1.3f1 with Burst 1.4.7 and Test Framework 1.1.24. I can ignore these warnings but they just add to the “noise” of warnings that I have to wade through now when diagnosing real build issues…

Unable to find player assembly: C:\UnityProject\Inferno\Temp\StagingArea\Data\Managed\UnityEngine.TestRunner.dll (shortened path)

Test Framework 1.1.26 - May 26, 2021
Burst 1.5.4 - May 17, 2021
Jobs 0.8.0-preview.23 - January 22, 2021

Unity 2020.3.9f1

1 Like

Exact same for me except I’m on Unity 2020.3.22f1.

Same problem :((
Unable to find player assembly: D:\UNITY\PROJECT!Die\Temp\StagingArea\Data\Managed\UnityEngine.TestRunner.dll
I’m on Unity 2020.3.22f1
…please help me

Same problem with unity 2021.2.7f

Same problem with 2021.2.8.f1 (macOS, building to android).