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.
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.
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.
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).
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…
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