Temp/UnityEngine.TestRunner.dll Error

I am getting this error called failed to copy temp/UnityEngine.TestRunner.dll to some random folder that i cant remember. Unity just does not respond. I close the un responding window through task manager and restarted it and lost all of my work. I would say unity is dumb and annoying because of this. My project took me 2 hours to make and it is all gone. HELP!

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--881386--crudware.png

[quote=“TechSideMC”, post:1, topic: 846703]
My project took me 2 hours to make and it is all gone.
[/quote]

I’m sorry you’ve had this issue. Please consider using source control in order to guard and protect your hard-earned work.

Personally I use git because it is free and there are tons of tutorials out there to help you set it up.

As far as configuring Unity to play nice with git, keep this in mind:

https://discussions.unity.com/t/736093/3

Here’s how I use git in one of my games, Jetpack Kurt:

https://discussions.unity.com/t/807568/3

Using fine-grained source control as you work to refine your engineering:

https://discussions.unity.com/t/826718/2

Share/Sharing source code between projects:

https://discussions.unity.com/t/719810/2

Setting up the right .gitignore file:

https://discussions.unity.com/t/834885/5

Generally setting Unity up (includes above .gitignore concepts):

https://thoughtbot.com/blog/how-to-git-with-unity

9 Likes

Thanks for the help.
I am using the Unity version 2020.3.12f1.
Will I be able to make it work if I built my project in Unity version 2019.4.17f1 and then opened it in Unity 2020.3.12f1?

[quote=“TechSideMC”, post:3, topic: 846703]
Will I be able to make it work if I built my project in Unity version 2019.4.17f1 and then opened it in Unity 2020.3.12f1?
[/quote]

Upgrades are one-way UP to higher version numbers only.

ALWAYS use source control properly and TEST that you have used it properly before upgrading.

Personally I use git because it is free and there are tons of tutorials out there to help you set it up.

As far as configuring Unity to play nice with git, keep this in mind:

https://discussions.unity.com/t/736093/3

Here’s how I use git in one of my games, Jetpack Kurt:

https://discussions.unity.com/t/807568/3

Using fine-grained source control as you work to refine your engineering:

https://discussions.unity.com/t/826718/2

Share/Sharing source code between projects:

https://discussions.unity.com/t/719810/2

Setting up the right .gitignore file:

https://discussions.unity.com/t/834885/5

Generally setting Unity up (includes above .gitignore concepts):

https://thoughtbot.com/blog/how-to-git-with-unity

I don't know how to set up source control or git and i am not wasting my time on it

I got the same error, I accidently linked an old project ID to my current project, that had the old colloborate version still on it instead of the Plastic SCM. So, I just created a new product ID and linked it to my new project and the error went away.

Every time this error occurs, I'm tired of correcting it by referring to this site... :(

1 Like

If you get this error, restart Unity. It should allow you to start unity in SafeMode. Once it comes up read the errors it gives you, most probably a file pointing to some plugin. It should state clearly where the file(s) are, delete them and Unity will restart by itself and your work is restored.

9284674--1301095--upload_2023-9-10_17-37-12.png

Worth pointing out that for the IDE packages you should remove the one's that you don't use, which may not necessarily be the ones highlighted here. ;)

Although in all fairness, VSCode ought to be removed indiscriminately. :smile:

Deleting the entries from json files is all that needs ? Engine clears the data afterwards ?

Or just remove them via the package manager.

1 Like

ahh Thank you,, still highly usefull post for Latest LTS here in 2024... <3

It would be great if Package Manager had a bulk removal option so manifest editing isn't required.

Guys, help. I removed all the unnecessary stuff but the stupid notifications still pop up like crazy.

If you get this error when building addressables after unity upgrade - you should migrate paths.

RemoteBuildPath -> Remote.BuildPath
RemoteLoadPath -> Remote.LoadPath

I was using custom build script and postprocessors that was trying to access old paths, so changing accessing to that paths in code are resolver the issue.