No explicit failure code handling for error of type 13

Hello Everybody,

I promise I googled the above error, and absolutely nothing came up, which was very surprising to me!

I'm new to Unity. I am running "2020.3.0f1 Personal" on macOS 11.1 Big Sur. I am creating some test project from some guy's YouTube video. I got to some point, where I started getting weird error messages, including the one in the subject. I first thought something is wrong with my code. I saved my scripts, deleted the project, created new project and this blank project already has this error in the status bar at the bottom:

"No explicit failure code handling for error of type 13"



So then I went to Unity Hub, uninstalled Unity, reinstalled (same version) of Unity, created new project, and the error is still there. Does anyone have any ideas?

 

Brand-new error to me too.

Remember when you test the latest and greatest Unity, you are in effect an unpaid test pilot and you are going to have to find and put up with a lot of bugs.

Try rolling back to 2019 LTS if you don't need anything beyond that and see if it works.

 

Installed 2019.4.22f1, same error! wow

 

Try resetting layout. I see you have the asset store window still open in your original shot, not sure if thats still present. Resetting the layout should remove it.

 

Do I do that by clicking "Layout" in the top right corner and choosing "Revert Factory Settings" ? I tried that, nothing really changed on the screen, and the error is still there. By the way, it's actually generating that error in console like several times per second:



The Assets looks like on screenshot below. It's literally a new empty project.



Should all of these things gotten reset when I delete the project and uninstalled Unity, reinstalled Unity and created new project? Is there maybe a procedure for MacOS that I should find that removes everything, including unity hub, and then start over maybe?

 

This is one approach to try.

If you click the error, in the console window bottom portion, is there any other useful stuff where the callstack would normally go? If so that might be some intel of where to fiddle around with, eg., if it said the error was coming from the package manager for instance.

 

Here is what I see in the console window, just the same error string. Looks like a bug. I must have clicked something.



I then found this article how to do full removal of Unity on macOS: https://nektony.com/how-to/uninstall-unity-on-mac, and followed it (without using those other apps they advertise), several folders had to be removed with some remaining unity settings. I then reinstalled unity hub and 2019 unity, created new project, and the error is... gone. Thank you for your help.

 

This started happening for me with 2020.3.0f1, too, but I did not see the same issue in 2019.4.5f1.
I noticed that my account was not signed in via Unity (even though it was in Unity Hub). I restarted my machine, relaunched Unity, and noticed that my account is signed in now (although I didn't do anything else to actually sign in). No more error.

 

Had this same issue and was about to format my mac, as it left all unity installations for all user accounts broken.

The key was to delete the unityhub directory in the "Saved Application State" directory mentioned in your link.

This bug is the second worst I've ever seen.
#1 was a visual studio downgrade after which windows 10 refused to boot.

 

I have the same problem. I deleted the unity hub Saved Application State and the problem still appears. Unity 2020.3.10f, mac. Any solution?

 

Appeared for me this morning. Wasn't there yesterday and I haven't explicitly changed editor versions. I want 2021 for various reasons, in particular latest Viz Scripting. Am preparing teaching materials and don't want to use older version.

Mac Unity 2021.1.7f1 but may try update to 12f1

 

Unity 2021.1.12f1 has that issue for me so that won't do it.

 

I had the same issue on my mac. I spoke to unity regarding it and we found out that it was because there was an instance of Unity Hub running on the second user account on my mac already using the port the editor uses to communicate to the Hub. Make sure there is not a second instance loaded of Unity Hub and then try again. Worked for me with error of type13.

 

Now I wish there was an option to set them to a different port. Here is exactly what the unity rep said:


Hi,

Thank you for contacting Unity about your issue.

In your log files I found the following issue: "Error: listen EADDRINUSE: address already in use :::39000".

Could you make sure that there is only one instance of Unity Hub running at the same time? If you find multiple instances of Unity Hub running please terminate one of them via the Activity Monitor.

Let me know if this fixes the issue or not. If you have any questions, feel free to ask.

Best regards,
Inga
Customer QA Team

 

Another reason for this happening, even if you do not have more than one hub running, is that if there is another user in MacOS running UnityHub (and you are not). Basically you cannot run Unity Hub or Unity across multiple users on on one Mac machine