Is this Unity just not liking my Australian internet tonight?
I’m getting pinged with this error every few seconds:
I would see it every now and again previously, and honestly just ignored it. But now they’re firing off every few seconds and completely polluting my console. Can’t get any debugging done at the moment.
This is on version 2023.2.9f1.
Unity if you’re going to phone home, at least don’t bother me about it.
Anyone got any input into this? Any Unity devs care to take a look? It’s seriously annoying to have this completely clogging up my console.
It’s worth noting this appeared out of nowhere (no version change), and is persisting through to a version update to 2023.9.10f1.
Yep, same problem here.
Apparently the issue is reported since 2023.2.5f1: Unity Issue Tracker - "Unexpected transport error from import worker 0" error is thrown when importing an asset
Never got it until the latest versions 2023.2.9 and .10.
I think it’s related to Project Settings → Editor → Asset Pipeline - Parallel Import setting being enabled.
Yeah I managed to track it down to something to do with asset importers. I’m not at my home computer, but from what I gathered it’s being caused by some data getting corrupted in the shadergraph cache. Though it seems to get triggered by anything trying to load an asset via AssetDatabase.
I’d have to dig out the logs I saved. Been meaning to update this post. But the stack traces start from a utility method of mine trying to load an asset, and then some internal ValidateMaterial methods for some reason despite not doing anything related to materials, and then a bunch of errors thrown by something to do with the shader graph cache.
Also FYI to anyone getting this issue, check your temp folder in Appdata. This error caused 10GB of log files to accrue in said folder for me… As well as about a gigabyte in my project’s Log folder.
Clearing the library folder seems to fix the issue until the data gets corrupted again.
Okay I believe this is due to Shader graph, at least in my case. I’ve noticed it only starts the session after Unity has compiled a shader made in shader graph (of which there is only one of in my project so far). The cache seems to be getting corrupted between sessions for whatever reason.
I’ve attached one of the asset importer log files.
There’s already a bug report so not sure if I should report another or not.
Every time this happens I have to delete the library folder, though if I so happen to be using said shader-graph materials, I have to do this a lot.
9671834–1378007–AssetImportWorker9.txt (60.1 KB)
I always get this error when I create a class directly in Rider instead of the Unity editor itself.
there may be multiple causes for the issue, but we fixed the one that was related to a crash after multiple code reloads in the asset import process - hopefully that helps, but let us know if you still experience issues
Yeah I found that in my case, it was due to some settings on that aforementioned shader I’d made in Shader Graph. Namely I hadn’t set it to a 2D shader. Once I changed that, the errors stopped.
In 6000.0.5f1 disabling Parallel Import has fixed the problem for me
Yeah, I just had to disable the parallel import in 6000.0.7f1 because I got end of file errors on random FBX files that have been working for a long time before the upgrade. I had to toggle the setting and restart the editor, then the re-import worked.
Hello, I was trying to add a Firebase database and I wanted to use it with Play Games and when I initialized Play Games I got this error that invades my console, parallel to that my partner was making graphics and I don’t know how to solve it, could you tell me where I deactivate what you indicate I use Unity 6 6000.0.020f1
After updating to Unity 6 6000.0.020f1, I’ve got those kind of errors constantly. It’s quite annoying 
My project still launches, the errors in the editor does not impact compiling of the game.
Same here. This started happening after updating from 6000.0.19f1 to 6000.0.20f1.
Regarding the comments above about disabling the parallel import setting. It has been disabled by default on my project. It doesn’t seem to make any difference.
I encountered the same error, and none of the suggested solutions worked for me. However, I was able to resolve the issue by switching platforms. In my case, I switched from Windows to Android and then back.
To do this:
This fixed the problem for me—hope it helps! 
I was having this problem as well and none of the solutions had any effect.
So it looked like this is not caused by any single issue. When that happens, my go-to is to delete my Library folder.
That got rid of it… for now anyway. You never know with this stuff. But it could have just been a result of some leftover flotsam from before I updated this project to 6000.0.
thanks you so much, it’s worked in 6000.0.21f1 for me
nope, in my case 6000.0.21f was not fixing it.
It appears if any object with custom shader ( shader graph) is selected.
In my case it means “every object” as I use one shader for 99% if assets in my game.
Im getting this error as well, 6000.0.21f1 (think it started happening from 6000.0.20f1).
I was also having the same problem which started in 6000.0.20f1 and continued with 6000.0.21f1 and none of the above solutions worked. But I noticed that some of my other projects were not exhibiting the error.
So what I did was to create a new project in Unity from scratch and then I copied over all my source code and plugins and then meticulously modified all the settings and added the layers etc. so that it was the same as the project giving the errors. I know I could have copied some of the settings files over but I wanted to keep it as “clean” as possible. It took a while but the error has now gone. I don’t know why, but it worked.
Make sure you back up your project just in case and it might be a good idea to tag it in your version control before proceeding
The issues is far from being solved. I’ve tried every “solutions” posted here and none of that works, i still having that problem and it is pretty annoying because it also makes the editor a bit slow too. In my case, the error is:
“Unexpected transport error from import worker 279. code=10054 error=An existing connection was forcibly closed by the remote host.”
