Unable to find player assembly

[KristenBoyGames]

i got an error that goes like this ```
Unable to find player assembly: C:\Users\Krist\Desktop\Loovtoo Folder\Loovtoo 2.0\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.5/Editor/BurstAotCompiler.cs:350)
Unity.Burst.Editor.BurstAotCompiler:OnPostBuildPlayerScriptDLLs (UnityEditor.Build.Reporting.BuildReport) (at Library/PackageCache/com.unity.burst@1.6.5/Editor/BurstAotCompiler.cs:208)
UnityEditor.BuildPlayerWindow:BuildPlayerAndRun ()

how to fix this and what is the issue?

[Kurt-Dekker]

Do you need the testrunner? Remove it if you don’t.

Extra unwanted packages in new projects (collab, testing, rider and other junk):

Temp/UnityEngine.TestRunner.dll Error

Recent versions of unity have an annoying habit of crapping useless packages into your project. When those packages inevitably have errors, this sort of thing happens. I have railed about it before. Go into the package manager and remove crap you don’t need, like the entire test runner and collab and whatnot. If you feel brave you can hand-edit the Packages/manifest.json file a lot faster than using the laggy package manager interface that only lets you remove one package at a time: [7287748-…

About the fastest way I have found to make a project and avoid all this noise is to create the project, then as soon as you see the files appear, FORCE-STOP (hard-kill) Unity (with the Activity Manager or Task Manager), then go hand-edit the Packages/manifest.json file as outlined in the above post, then reopen Unity.

Sometimes the package system gets borked from all this unnecessary churn and requires the package cache to be cleared:

Unity3D Package Cache errors(?)