Build Errors after Upgrading to Unity 2017.1.0f3

Since we upgraded to Unity 2017.1.0f3 we get the following errors during build:

but in Library, there is no "unity editor resources" file or folder.

That didn't happen before with 5.6.1f1.
Non of the cameras have the "hdri" flag checked. Any ideas what this could be and how to fix it?

 

We're experiencing the same issue.

 

Same for me

I tried to remove Library folder and restart, didn't fix, I moved from 5.6.1 too, my project does not compile with cloud either, but with a different unknown error

 

I've solved the problem. After updating project lighting settings were changed. Cubemap for Environment Reflections was set to "DefaultHDRI" (which doesn't exist as an saved asset).

 

We have skybox as a source, but changing source to custom and the going back to skybox fix the issue too. (cubemap was set to none).

Thanks !!

 

That solved it for me as well! Thanks for the solution!

 

I tried your solution and it didnt work . Used skybox as source and also tried my reflection probes in custom mode. No success. Still gives the same error.

Update: Fixed by creating a new scene, copying all the scene objects as is, and pasting them in a new scene. The new scene does not give the error when building.

 

Man, thank you ! I've been facing this issue for the past 4 hours ! And I just wanted to build a simple test scene x)

 

I get similar errors when I try to build for Windows (Didn't check other targets)

1:

2:

I have sharedassets3?
None of these solutions here worked for me...

I checked all the scenes I'm using and they all have no cubemap selected in the scene lightning window.

 

I had the same problem and resovle this way:

In every scene set in Environment Reflections -> Source some random cubemap, build game with no errors, back to editor and set there skybox. Thanks for tips guys from upper

 

It is the experimental dev look tool that applies a DefaultHDRI cubemap to the environmental reflections source of your currently open scene. D'oh!

 

I had to change the Skybox material as well as the cubemap and this fixed the issue for met - Skybox/Cubemap was the material that was set which i asumme used the DefaultHDRI cubemap as well.

 

Thanks, it worked for me!

 

In Unity 2017.1.0f3, I resolved this issue without having to make a new scene.
I did this by doing the following process:

1. Change Lighting->Environment->Environment Reflections->Source to Skybox.
2. Change the Skybox Material to some other skybox, NOT the default skybox.
3. Delete LightingData and ReflectionProbes for the scene.
4. Rebake Lighting.

 

Hi, i tried what is described above (points 1 and 2) but with no success so far. My project is in 2D and use no lighting at all: i don't have Lighting Data, and i don't even found any setting regarding Reflection Probes. And i don't baked lights.

My game built still spit that same error.

Edit: Built success after repeating operation for my other scenes...

 

thanks everybody i had this issue and solved it with changing environment reflections source to skybox, this needs to be done on all scenes in the project even if they are not part of the build.

thanks

 

I'm getting the error with this:

An asset is marked with HideFlags.DontSave but is included in the build:
Asset: 'Library/unity editor resources'
Asset name: sv_label_3

This is in 2017.1.1f1

Does anyone know the solution? thanks.

 

This was also the solution for our project. I also had to remove the default skybox material.

 

Did you ever figure this out? I have the same issue with same name - sv_label_1

 

Thank you all guys
Unity make changes in 1 scene just because he want hahaha XD

 

Does anyone have any idea of how to pinpoint which scene might be causing the issue in the build?

 

Just as an update to my issue - This was being caused by an asset called Easy Save 3.

Anything being serialized with the hideflag.hide would cause this. So in my case it was any transform that had one of unity's custom icons (like the red diamond or green sphere, etc) added to it was getting caught and causing the error.

 

@Fairennuff good catch, I've actually got ES2 installed and havent bumped up to ES3 yet, but would assume similar issues.

What did end up doing to alleviate the issue though? Just clearing the custom transform to anything that was tied to easy save?

 

In my case it was es2 or 3. Tried both and they both caused it. I emailed their support and they sent me an updated script. They say it's fixed in the newest version but when I updated the asset and reimported I got the error and had to replace the script again. So either they overwrote the fix, or my unity isn't pulling the newest version.

 

Awesome, good to know @Fairennuff I'll give a shout to Joel then. Thanks for letting me know about this!

 

I had this, too. However, I was pretty sure we *only* had regular skyboxes. One scene randomly had that cube thing. What's up with this? It was only after I upgraded from Unity 2018.2 >> 2018.3 and ported from Nested Prefabs to native.

EDIT: Hmm, the suggestions here didn't seem t resolve it :/

Related - https://www.reddit.com/r/Unity3D/comments/aosw9i/failed_to_build_after_upgrading_to_20183_from/

 

For me I deleted an SkyBox from my scene and regenerated the lighting