Bug 2022.02.0b9 Asset has disappeared while building player to 'globalgamemanagers.assets'

When i start a build like normal, it shows me the following error.

Asset has disappeared while building player to 'globalgamemanagers.assets' - path '', instancedID '-43676'

UnityEditor.BuildPipeline:BuildPlayer (UnityEditor.BuildPlayerOptions)

WORKAROUND: After some search, i found some bugs from several years ago, showing a workaround: Close all Unity Windows, Restart Unity, directly start the compile without opening windows. => Worked... But not very useful

Just opening the console brings that error again, so another restart is needed..

ps.: Same at 2022.02.0b8 and 2022.02.0b9.

 

I've had files disappear due to antivirus quarantine - solution for me was whitelisting engine and project folders. If doesn't help in your case, maybe helps someone else. I'm using 2022.2.0b9 as well but have had no such issue (so far).

 

No antivirus in use here. Also why its working when unity starts with closed unity-tabs and directly the build is started So i think, it has to do something with unity itself.

 

Update: I Nailed it down to Console, Game and Scene Window. They has to be never opened, to prevent this error.

 

I have same issue. Unity 2022.2.0b11 still has this issue.
Windows : OK
Mac Intel : Error
Mac M1 : Error
So I can't build iOS player

 

Same for me on 2022.2.0b15. It happens sometimes, but not always; usually it suffices to try building again.

 

We were getting the same, ever since 2022.2 beta.
Waited out for the official 2022.2.0f1 release, but still getting the same.

So +1 on this.
It's preventing us from upgrading to the new tech stack. Which we want for Entities 1.0 and other editor ameliorations
Anyone managed to fix this ?

 

I also still got that error also with the 2022.2.0f1.
@Mic_Emond: My workaround i mentioned in the first post is still working for me. Sometimes i need to restart one more time. Its pretty annoying, due to the compile took a very long time and it just crashes at the end of it...

The Forum has been moved to achived now...
Is anyone from Unity that have this bug noticed?

Update: Looks like in Unity 2023.1.0a22 it seems not happening, but that editor crashes way too often for other reasons...

 

@StefanWo Thanks for the confirmation.
Sadly we're using a build machine and running builds through the command line and they still fail. (they also fail when trying from the editor locally)
I've started a new thread in the "Editor" part of the forum since 2022.2 is out of beta now. But it's quickly getting burried.
(here it is for anyone interested)
https://forum.unity.com/threads/build-fails-after-update-to-2022-2-0f1.1373190/

Going to 2023 isn't a good move for us as we'd like to ship within the 2022 LTS cycle

 

Thanks for posting it there too. I discovered some other forum entries, related to the UI-Package, that would make sens, that not using it in the editor fixes this issue somehow. In the new Version i had troubles even when i tried to do that, and it worked even with all windows open. Its really strange...

I could fix it from time to time when playing around with packages, so adding and removing them. Than directly after the restart of the Editor, i can build it once without that error. It's also mentioned here as a workaround:
https://forum.unity.com/threads/dot...ets-is-corrupted-in-standalone-build.1031437/

Update: After its compiled, i get strange memory corruptions, maybe its related to it, maybe not. I have to downgrade again to Entities 0.51 to continue working... Hope this errors got fixed soon

 

New Entities prev-44 with the recommended Unity version => still the same. But after compiling a 2. time it worked. No idea...

I can't just remove the entities, due to i build my project on it.

 

Using pre-65 and Unity 2022.2.13 => still the same... Anyone an idea what can be the cause of this strange bug, or ideas how to figure this out?

 

Same bug here, Unity 2022.2.14f1... show stopper.

 

Good to hear, that i'm not the only one

I'm now on Unity 2022.2.16 and got once an additional other error: (the original one still appears when trying to build again)

Code (CSharp):

1. Building - Failed to write file: resources.assets

Is this maybe somehow related?

 

Same here with Unity 2022.2.19f1 and WebGL build.

 

Same here with Unity 2022.2.21 building for Android:

Asset has disappeared while building player to 'globalgamemanagers.assets' - path '', instancedID '-128600'
UnityEngine.GUIUtilityrocessEvent (int,intptr,bool&)

 

Same bug on 2023.3.0 lts, can we get a Unity employee in here to help resolve? Pretty disruptive and unexpected in an lts release...

 

I submitted IN-44206 case number for u to investigate this build error.

 

We are seeing this bug in Unity 2019.4.28f1 while building to iOS, in a project that previously built fine in 2019.4.12f1.

 

We're seeing the same issue in version 2022.3.0.

If the editor has been open for some time, the build process fails, but if you close and reopen Unity, the build always works. I have no idea what causes it.

 

I got as far as 2019.4.16f

2019.4.17f and up seem to be the start of this problem. For me.... on a Mac, using Builtin, for iOS builds.

 

How about using some reasoning, insight and inquisitiveness into what and hows that could be causing this?

 

This is still occurring for me as of 2022.3.5f1 fwiw. If I close the editor and build again its fine but that's a hacky workaround. (WebGL builds)

 

Currently at latest 2022.3.6f1 my project when trying to build player runtime sometimes will get another weird fatal error that tells me splash screen cache at Library is missing and then crash.

 

We have the same error while building standalone. Android and iOS don't have this problem.

Asset has disappeared while building player to 'globalgamemanagers.assets' - path '', instancedID '-379362'
UnityEngine.GUIUtilityrocessEvent (int,intptr,bool&)

 

The raise of this bug getting now more and more random. It seems for me it helps just to retry over and over again, till its working. Sometimes it need 5 tries to finish successfully. Sometimes its failing directly after another build for another platform was successful.

For everyone who also have a custom build script, here my quick dirty "workaround":

Code (CSharp):

1.  
2.        var unityBugAppeared = false;
3.         Application.LogCallback onLogMessage = (string condition, string stackTrace, LogType type) => {
4.             if (type == LogType.Error && condition.Contains("globalgamemanagers.assets")) {
5.                 Debug.Log("Detected Unity bug. Marking for retry");
6.                 unityBugAppeared = true;
7.             }
8.         };
9.         Application.logMessageReceived += onLogMessage;
10.         Application.logMessageReceivedThreaded += onLogMessage;
11.         UnityEditor.Build.Reporting.BuildReport report;
12.         try {
13.             report = BuildPipeline.BuildPlayer(options);
14.         } finally {
15.             Application.logMessageReceived -= onLogMessage;
16.             Application.logMessageReceivedThreaded -= onLogMessage;
17.         }
18.  

 

From the QA reply mentions that it's caused by official package that needs to fix by official. Anyway I think Unity editor needs to improve to make it able to just log the exact error that tells u which code with line number goes wrong.

 

For me personally it was fixed when I added all available Locales to Localization settings. I am using Unity Localization package and I filtered available languages in my app by excluding some Locales from Available Locales in Localization settings. After I restored all of them in Available Locales list (I filter them in runtime with a config now) the problem has gone.

 

We need some help here. How could we narrow down the investigation? I'm not sure what to look for, or where to look for it.

Could we dump all instance IDs in a text file at end of step 1, to get more information about he culprit? Could this work?

 

Hi @AndrewSkow
So I have dumped all instances IDs just like I said in my previous post.
I found that on one of my case where the bug happened, the missing instance ID was -10690280, I couldn't not find it in my dumps, but I found two instance IDs nearest to that number:
PreloadData : -10690284
PreloadData : -10690282

Could PreloadData be a clue of what could happen? Could it be something to investigate for?
The only thing I can find in Unity official documentation is https://docs.unity3d.com/Manual/ClassIDReference.html where PreloadData appears in a list.