Search Issue Tracker
Active
Under Consideration for 2021.3.X
Votes
4
Found in
2021.3.14f1
2022.1.23f1
Issue ID
UUM-20020
Regression
No
"Unable to find player assembly" Warning appears when a Sample is Built
How to reproduce:
1. Create project with Sample "Cinematic Studio" (for example)
2. Run and Build the project
3. Observe Console
Actual result: "Unable to find player assembly" Warning appears
Expected result: Player is built without Warnings
Reproducible with: 2021.3.14f1, 2022.1.23f1
Couldn't test with: 2020.3.42f1, 2022.2.0b16, 2023.1.0a20 (No Sample)
Tested on: Windows 11
Warning message: "Unable to find player assembly: C:\t\My project (2737)\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.6.6/Editor/BurstAotCompiler.cs:350)
Unity.Burst.Editor.BurstAotCompiler:OnPostBuildPlayerScriptDLLs (UnityEditor.Build.Reporting.BuildReport) (at Library/PackageCache/com.unity.burst@1.6.6/Editor/BurstAotCompiler.cs:208)
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)"
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Add comment