HideFlags.DontSave is included in build [SOLVED]

[nFighter]

After adding Easy Save 3 Manager to my scene I can't build the project anymore. It's always some objects with errors like this:

Code: Select all

An asset is marked with HideFlags.DontSave but is included in the build:
Asset: 'Library/unity editor resources'
Asset name: VideoClip Icon
(You are probably referencing internal Unity data in your build.)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

and I don't have any idea how to find these objects and fix it. I can't find anything with a title like "VideoClip Icon" in my project

Since I didn't use EasySave Manager for anything except Read/Write files with runtime generated data and variables, I actually didn't need any references in the ES manager at all. Is there a way to have an empty manager in the scene?

Or, is there a way to somehow find these objects and fix them?

[Joel]

Hi there,

That's strange, we had reports of this quite a few versions ago but was resolved. Just to check, are you using the latest version of Easy Save?

If you are, please could you private message me a basic project which replicates this?

All the best,
Joel

[nFighter]

Oh, seems like I found the issue!
I'm using the "Hierarchy Icons" asset to sort my objects in hierarchy, and of course, the icon component can exist only in the editor. But ES3 Manager create a reference for these components and it end up in the build error.

is there a correct way to solve this situation?
I can just delete the hierarchy icon from the scene, but maybe there is a proper solution?

BTW. Here is the icon hierarchy asset, it's free but very useful!
https://assetstore.unity.com/packages/t ... ons-163353

[Joel]

Hi there,

Thanks for the info, that's allowed me to track down the issue. It looks like it's setting it's HideFlags at a strange time, meaning Easy Save doesn't know it needs to be hidden until it's too late.

I've added some code to account for this at our end which resolves the issue. If you private message me your invoice number I can send this update over right away.

All the best,
Joel

[nFighter]

Oh, great! I just come back here to report about the workaround I made up with the hierarchy asset, but dealing with the ES3 asset directly would be much better! Thanks