Asset has disappeared while building player

Unity Engine
1

I tried to build our project with 2020.1.0a25

Does this error message rings a bell to anyone?
I’ve never seen it before.
This was the first time I tried to build our project with 2020.1

Asset has disappeared while building player to ‘archive:/BuildPlayer-Design/BuildPlayer-Design.sharedAssets’ - path ‘’, instancedID ‘-74116’
UnityEditor.BuildPipeline:BuildAssetBundles(String, AssetBundleBuild[ ], BuildAssetBundleOptions, BuildTarget)

Other messages are textmesh pro specific

I have 2 of these:

NullReferenceException: Object reference not set to an instance of an object
TMPro.TMP_SubMeshUI.UpdateMaterial () (at Library/PackageCache/com.unity.textmeshpro@3.0.0-preview.1/Scripts/Runtime/TMP_SubMeshUI.cs:691)
TMPro.TMP_SubMeshUI.SetMaterialDirty () (at Library/PackageCache/com.unity.textmeshpro@3.0.0-preview.1/Scripts/Runtime/TMP_SubMeshUI.cs:601)
UnityEngine.UI.MaskableGraphic.OnValidate () (at C:/Program Files/Unity/Hub/Editor/2020.1.0a25/Editor/Data/Resources/PackageManager/BuiltInPackages/com.unity.ugui/Runtime/UI/Core/MaskableGraphic.cs:176)
UnityEditor.BuildPipeline:BuildAssetBundles(String, AssetBundleBuild[ ], BuildAssetBundleOptions, BuildTarget)

I think it happens in 2019.3 but it won’t cause the build to bail.

I also have 2345 of these:

Material doesn’t have a float or range property ‘_CullMode’
UnityEngine.Material:GetFloat(String)
TMPro.TMP_SubMeshUI:UpdateMaterial() (at Library/PackageCache/com.unity.textmeshpro@3.0.0-preview.1/Scripts/Runtime/TMP_SubMeshUI.cs:691)
TMPro.TMP_SubMeshUI:SetMaterialDirty() (at Library/PackageCache/com.unity.textmeshpro@3.0.0-preview.1/Scripts/Runtime/TMP_SubMeshUI.cs:601)
UnityEditor.BuildPipeline:BuildAssetBundles(String, AssetBundleBuild[ ], BuildAssetBundleOptions, BuildTarget)

These are new in 2020.1

2

Hmm, was able to build on the second try.
I still has the TMPro errors, so it had nothing to do with the original issue

3

Could you please try upgrading TMP to the latest version and see if this helps?

Preview 4 included this fix: Fixed potential Missing Component Exception that could occur when a TMP_SubMeshUI object is created.

https://docs.unity3d.com/Packages/com.unity.textmeshpro@3.0/changelog/CHANGELOG.html#changes-16

4

I just encountered this issue myself and couldn’t figure it out. So I finally tried doing a “Reimport All” which then generated another error message related to a third-party asset I had installed. Thinking one of the asset files may have gotten corrupted somehow, I redownloaded the asset from the Asset Store, then imported it (the asset had since been updated, so it upgraded the asset in the process), and that seemed to fix it. So if you get this, check any recently modified assets, and if you have no idea where to start, try reimporting. Hopefully you’ll get some kind of error during the reimport that will identify which asset(s) caused the problem. Then just completely replace/reinstall those assets.

1 Like
5

I had also this error “Asset has disappeared while building player”. At first I got unity build successfully after restarting computer, but later that problem comes back to stay. But finally I found a solution. For me it was a faulty RAM. So if you are getting this error check your system memory to make sure it’s not failing. And that was only problem with that faulty RAM. And it was always the same scenes that crashed build and project was size of 90Gb and build over 10Gb.

6

This happened to me on an Apple M1 chip Silicon machine. I fixed this by navigating to the build folder (output dir for game) and deleted the previous already existing build. It appeared to happen after I changed the product name and studio info. Try this for anyone in the future encountering this problem.

7

Tried this. Tried formatting the entire PC and installing fresh window. Tried stripping the project of almost everything.

Nothing works.

8

Sorry to hear that man. Let me know if I can be of help in anyway.

9

I suppose there are several possibilities reason for that and the problem on my side was really the RAM fault

10

oddly in more recent versions of Unity (specially Alphas) it happens much less often.

11

Sometime making a prefab, for whatever reason, will upset unity it seems. I just deleted two prefabs I had made during this game version edit and now it works.

12

According to chatGPT this is caused my a corrupt or missing “asset” in my case, it was just two grass prefabs.

13

One thing you can do that worked for me was finding the asset in the path, then selecting “reimport” in the context menu. You can do that for whole folders or you can also “reimport all”, but depending on your project’s size it could take a while to reimport all assets :stuck_out_tongue:

14

Just delete Library\Bee folder, and try clean Build.

3 Likes
15

Bro, this is the best advice! :wink:

1 Like
16

Error here too, what I found to work is to change the change the compression to Brotli, but it takes so long

17

Here it happens when “Script Debugging” is ON. Otherwise everything works fine.

18

After almosth 7 hours, I finally got it working, it was not the library, or a clean build, it was just a gameobject with down sindrome that was messing with the build, how did I find it, just do the following, if you are trying to build multiples scenes, you need to identify wich one has the infected game object , for me was the terrain that has a GPU instancer script with a componet to that no longer was working for a reason I did not know,

1- identify the scene with the issue.

try to build all scene at once, you will get the error ( [Asset has disappeared while building player]. then, try to build each scene separate until you get the scene that has the issue

2-identify the gameobject with the issue
in my experience the issue is cause do to a component that is interfering with the build, in order for you to find it, you need to do this: take half of your gameobjects in the scene and copy them, then delete them, and the try to build the game, if you still got the issue, just paste all your game objects back in to your scene and do the same with the other half, until yopu get a build success, once you identy the half of the gameobject with that is causing the issue, repeat the process of deleting each game object intil you find the one with the issue, you will know which gameobject is the infected one once you get a success build after deleting the game object.

3- replace the game object,

once you identified the gameobject that has the issue, replace it with a brand new copy, or re import the asset that contains the componet and re attach it to the gameobject, that is was it for me, hope this wroks for you, hit me up by email if you want me to help you with yours wellington.hiciano25@gmail.com