Reloading Domain Stuck

Unity Engine
, , , , ,
1

Hi everyone,

I’m working on a little android game which relies on Google play services and Wwise (I mention them just in case, even if I don’t think the cause the problem).
Lately, even after changing a single line of code, the “Reloading Domain” process forces me to kill Unity and re-open it: this is VERY annoying.
I know that this process can be disabled by settings, but I need it (without it, the wwise engine does not work properly).
Is there a way to avoid or mitigate this problem?

Thank you in advance :slight_smile:

2

Close the project, delete the folders Library, Obj and Temp (if it exists), wait till delete completed and re-open the project.

If this doesn’t fix it, be sure to upgrade to the latest patch release (ie 2022.3.5f1 to 2022.3.48f1) in case it’s a known and fixed issue.

4

Hi, I’ve been experiencing the same issue and am also using Wwise. The issue for me started last week, around the same time that I changed these Wwise settings in the Edit → Project Settings → Wwise Initialization tab:
image

By default those settings were unchecked. I checked both of them, and thats when the issue seemed to have started for me. I just set them both back to being unchecked, and have run the game probably 20 times now without an issue. I can’t 100% confirm that my issue was due to that setting, but just wanted to mention it real quick in case it helps

5

This worked for me:

  • while reloading domain is in process/stuck, go to Visual Studio or whatever your code editor is,
  • make some random changes to any script (I usually just remove a semicolon),
  • then undo the change by hand (i.e. not by using the Undo command. I typed a semicolon back).
  • Save the script (even though nothing was changed).
  • Unity will move pass “reloading domain” and function normally.
2 Likes
6

This unironically will work as I found out my problem was that I declared an instance which didn’t exist and when compiling my internet connection suddenly went off, resulting this. Changing the code and saving it mostly fixes it

7

For me it was Unity Version Control, I had disabled it and it didn’t seem to be active anymore. Once I removed the package the problem went away.