Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice
New Forum User Notice Update to the Unity Editor Software Terms

Unable to find player assembly BURST AOT Compiler

Discussion in 'Package Manager' started by YURI_uwu, Jul 21, 2020.

  1. YURI_uwu

    YURI_uwu

    Joined:
    Mar 12, 2019
    Posts:
    12

    
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.
     
    YURI_uwu, Jul 21, 2020
    #1

  2. tim_jones

    tim_jones

    Unity Technologies

    Joined:
    May 2, 2019
    Posts:
    282
    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.
     
    tim_jones, Jul 21, 2020
    #2

  3. YURI_uwu

    YURI_uwu

    Joined:
    Mar 12, 2019
    Posts:
    12
    Even with the error present, is the Burst compilation enabled in my build?
     
    YURI_uwu, Jul 21, 2020
    #3

  4. edecr

    edecr

    Joined:
    Feb 21, 2014
    Posts:
    2
    Bump, any reply about this question?
     
    edecr, Jul 28, 2020
    #4

  5. ndrm

    ndrm

    Joined:
    Jul 25, 2020
    Posts:
    8
    Hi.. can i get some help please.. https://forum.unity.com/threads/cannot-establish-connection-diagnose-help.938618/
     
    ndrm, Jul 28, 2020
    #5

  6. ek578

    ek578

    Joined:
    Jun 25, 2020
    Posts:
    5
    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?

    Code (CSharp):
    1.  
    2. Unable to find player assembly: /content/svo-games/Project/Temp/StagingArea/Data/Managed/UnityEngine.TestRunner.dll
    3. UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
    4. UnityEngine.DebugLogHandler:LogFormat(LogType, Object, String, Object[])
    5. UnityEngine.Logger:Log(LogType, Object)
    6. UnityEngine.Debug:LogWarning(Object)
    7. Unity.Burst.Editor.BurstAotCompiler:OnPostBuildPlayerScriptDLLsImpl(BuildReport) (at Library/PackageCache/com.unity.burst@1.2.3/Editor/BurstAotCompiler.cs:212)
    8. Unity.Burst.Editor.BurstAotCompiler:OnPostBuildPlayerScriptDLLs(BuildReport) (at Library/PackageCache/com.unity.burst@1.2.3/Editor/BurstAotCompiler.cs:90)
    9. UnityEditor.Build.BuildPipelineInterfaces:OnPostBuildPlayerScriptDLLs(BuildReport) (at /home/builduser/buildslave/unity/build/Editor/Mono/BuildPipeline/BuildPipelineInterfaces.cs:487)
    10. (Filename: Library/PackageCache/com.unity.burst@1.2.3/Editor/BurstAotCompiler.cs Line: 212)
    11.  
    12. /content/svo-games/Project/Library/PackageCache/com.unity.burst@1.2.3/.Runtime/bcl.exe exited after 3385 ms.
    13. /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
    14. (Filename: unknown Line: 0)
    15.  
    16. clang: error: linker command failed with exit code 1 (use -v to see invocation)
    17. (Filename: unknown Line: 0)
    18.  
    19. BuildFailedException: Burst compiler (1.2.3) failed running
    20.  
    21. stdout:
    22. The native link step failed. Check previous exception in the log - linker command line : "/usr/bin/clang "@/tmp/tmp30e5e4dd.tmp""
    23. stderr:
    24. /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
    25. clang: error: linker command failed with exit code 1 (use -v to see invocation)
    26.  
    27.   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
    28.   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
    29.   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
    30.   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
    31.   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
    32.   at UnityEditor.Build.BuildPipelineInterfaces.OnPostBuildPlayerScriptDLLs (UnityEditor.Build.Reporting.BuildReport report) [0x00033] in /home/builduser/buildslave/unity/build/Editor/Mono/BuildPipeline/BuildPipelineInterfaces.cs:487
    33. UnityEngine.DebugLogHandler:Internal_LogException(Exception, Object)
    34. UnityEngine.DebugLogHandler:LogException(Exception, Object)
    35. UnityEngine.Logger:LogException(Exception, Object)
    36. UnityEngine.Debug:LogException(Exception)
    37. UnityEditor.Build.BuildPipelineInterfaces:OnPostBuildPlayerScriptDLLs(BuildReport) (at /home/builduser/buildslave/unity/build/Editor/Mono/BuildPipeline/BuildPipelineInterfaces.cs:491)
    38. (Filename: Library/PackageCache/com.unity.burst@1.2.3/Editor/BurstAotCompiler.cs Line: 752)
    39.  
    40. Error building Player: 3 errors
     
    ek578, Jul 29, 2020
    #6

  7. jjejj87

    jjejj87

    Joined:
    Feb 2, 2013
    Posts:
    1,109
    Do we have an ETA for the fix and the dates for backport? Thanks
     
    jjejj87, Aug 18, 2020
    #7
    unity_dbxrj86RpmQtkg likes this.

  8. tim_jones

    tim_jones

    Unity Technologies

    Joined:
    May 2, 2019
    Posts:
    282
    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.
     
    tim_jones, Aug 18, 2020
    #8

  9. tim_jones

    tim_jones

    Unity Technologies

    Joined:
    May 2, 2019
    Posts:
    282
    @ek578 the actual error there is hiding under the warning:

    Code (CSharp):
    1. /content/svo-games/Project/Library/PackageCache/com.unity.burst@1.2.3/.Runtime/bcl.exe exited after 3385 ms.
    2. /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
    3. (Filename: unknown Line: 0)
    4. clang: error: linker command failed with exit code 1 (use -v to see invocation)
    5. (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?
     
    tim_jones, Aug 18, 2020
    #9

  10. JRooth

    JRooth

    Joined:
    Jun 23, 2020
    Posts:
    6
    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.
     
    JRooth, Aug 27, 2020
    #10

  11. JRooth

    JRooth

    Joined:
    Jun 23, 2020
    Posts:
    6
    bump
     
    JRooth, Sep 8, 2020
    #11

  12. tim_jones

    tim_jones

    Unity Technologies

    Joined:
    May 2, 2019
    Posts:
    282
    Hi @JRooth - yes, this is the right thread :)

    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).
     
    tim_jones, Sep 8, 2020
    #12

  13. LogaNRV

    LogaNRV

    Joined:
    Jun 3, 2017
    Posts:
    35
    Sorry for the bump.

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

    build warning.png

    (Edit: also with Burst 1.4.6)
     
    Last edited: Mar 29, 2021
    LogaNRV, Mar 27, 2021
    #13

  14. dreasgrech

    dreasgrech

    Joined:
    Feb 9, 2013
    Posts:
    205
    I'm getting the same two warnings on Unity 2020.3.1f1 LTS using Burst 1.4.6
     
    dreasgrech, Mar 27, 2021
    #14
    CookieStealer2 likes this.

  15. Rabadash8820

    Rabadash8820

    Joined:
    Aug 20, 2015
    Posts:
    87
    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...
     
    Last edited: Apr 15, 2021
    Rabadash8820, Apr 14, 2021
    #15

  16. HuySora

    HuySora

    Joined:
    Feb 27, 2021
    Posts:
    6
    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

    https://paste.myst.rs/2crmze3p
     
    HuySora, May 31, 2021
    #16
    fendercodes likes this.

  17. fendercodes

    fendercodes

    Joined:
    Feb 4, 2019
    Posts:
    190
    Exact same for me except I'm on Unity 2020.3.22f1.
     
    fendercodes, Nov 14, 2021
    #17

  18. drland0813

    drland0813

    Joined:
    Aug 1, 2021
    Posts:
    1
    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
     

    Attached Files:

    • 2d.PNG
      2d.PNG
      File size:
      32.3 KB
      Views:
      259
    drland0813, Nov 17, 2021
    #18

  19. LukaH00

    LukaH00

    Joined:
    Jan 7, 2021
    Posts:
    3
    Same problem with unity 2021.2.7f
     
    LukaH00, Jan 9, 2022
    #19

  20. nooxouille

    nooxouille

    Joined:
    Aug 29, 2018
    Posts:
    24
    Same problem with 2021.2.8.f1 (macOS, building to android).
     
    nooxouille, Jan 21, 2022
    #20

  21. tim_jones

    tim_jones

    Unity Technologies

    Joined:
    May 2, 2019
    Posts:
    282
    Thanks all - I've flagged this to the relevant teams inside Unity.
     
    tim_jones, Jan 25, 2022
    #21
    nooxouille likes this.

  22. tim_jones

    tim_jones

    Unity Technologies

    Joined:
    May 2, 2019
    Posts:
    282
    tim_jones, Jan 25, 2022
    #22
    nooxouille likes this.

  23. HoShiNoNa

    HoShiNoNa

    Joined:
    Apr 11, 2022
    Posts:
    1
    Same problem for Unity2020.3.32&2020.3.33. I failed to get any "exe" for my projects and have no idea how this happens :(
     
    HoShiNoNa, Apr 20, 2022
    #23

  24. tim_jones

    tim_jones

    Unity Technologies

    Joined:
    May 2, 2019
    Posts:
    282
    Hi @HoShiNoNa - the issue in this thread is "only" a warning, and shouldn't affect whether or not you get a successfully-compiled player. If you're getting any errors in the console when building a player, please could you post the details into a new forum thread?
     
    tim_jones, Apr 20, 2022
    #24

  25. Esend

    Esend

    Joined:
    Nov 13, 2021
    Posts:
    7
    I am also getting a nearly identical error as JRooth. I'm using 2020.3.24f1.

    Unable to find player assembly: D:\Game Development\Projects\MyGame\Temp\StagingArea\Data\Managed\UnityEngine.TestRunner.dll
    UnityEngine.Debug:LogWarning (object)
    Unity.Burst.Editor.BurstAotCompiler:OnPostBuildPlayerScriptDLLsImpl (UnityEditor.Build.Reporting.BuildReport) (at Library/PackageCache/com.unity.burst@1.3.4/Editor/BurstAotCompiler.cs:286)
    Unity.Burst.Editor.BurstAotCompiler:OnPostBuildPlayerScriptDLLs (UnityEditor.Build.Reporting.BuildReport) (at Library/PackageCache/com.unity.burst@1.3.4/Editor/BurstAotCompiler.cs:163)
    UnityEngine.GUIUtility:processEvent (int,intptr,bool&)

    I understand that this is just a "warning" however it is the only warning coming up, no errors. Currently my game works exactly as expected in the editor and in play mode, however once I attempt to do a standalone PC build I get the above warning and ALL of my monobehavior scripts do not work. As in behaving like the scripts don't even exist, that kind of do not work.

    Any help would be greatly appreciated.

    Edit: Correction, my monobehaviors are working correctly. However all of my scripts that inherit from the XR Interaction Toolkit do not work. Is there a specific namespace I need to use for unity to compile my scripts? I'm at a complete loss as it's building "successfully" and showing no errors, just this missing player assembly warning.

    Second Edit: Disabled the burst compiler. It's no longer giving me the missing player warning, as expected, but my scripts still are not working. I realize this is now outside the scope of this forum post, if anyone could point me in the right direction to get some help with this I would be very grateful.
     
    Last edited: Apr 21, 2022
    Esend, Apr 21, 2022
    #25

  26. GXMark

    GXMark

    Joined:
    Oct 13, 2012
    Posts:
    506
    We know thats its a warning but surely its untidy to take that stance on warnings in an LTS version ?
     
    GXMark, May 13, 2022
    #26
    Hoichael likes this.