Build stuck on packaging assets - resources.assets

Hello I have this problem where I try to build, even a nearly empty scene and the editor stuck in the build.

Googling I read some similar problem talking about shader compiling broken for some reason, I also have some shader compiler process going on at high cpu % in background so that may be it.
But the project has lot of stuff and many assets and it would be really hard to identify which one, also I dont get why Unity try to pack the assets to build an empty scene..
Is there a way to make the build verbose or similar so to know at which point building the project slows down?

Anyway any help would be appraciated.

 

Try to uncheck the "Auto" checkbox from Window > Lighting

 

That was not the case, I mean it happens very often cause for some reason unity sometimes returns the baking to auto even if I disable it but in my case I had it off, also easy to spot cause you see the bottom right blue bar of lighting.

 

I have exactly the same problem!?!

Unchecking "Auto" does not help, also I tried to export the whole project and import to a new empty project without success. Delete "library" folder does not fix it, too.

Hope someone here knows the answer for this issue.

 

It is very likely some incompatible shader, I have a bunch of assets with shaders, once I removed them all it started work again, even though I can't be 100% sure since I removed a lot of scripts and models and stuff, my best guess is some old shader though

 

Do you use "VolumetricFog&Mist" ? This caused the issue in my case! After deleting this asset from my project, everything is working again. I have contacted the developer just now.

 

Nope, but thank you anyway.

 

I am having the same issue. It took at least 8 hours for just one build. I think there are some incompatible assets. I am using version 5.5.1p1. I haven't tested on other version.

 

Hi there,
"Uber-shaders" use shader keywords which are responsible of producing many shader variants during the first Build (after that they get cached). They do to improve performance by reusing the same render Pass to combine many effects or features in optimized way so only the required code for the configured feature set is executed in the GPU.
Usually the asset documentation states which shader keywords can be removed (by editing the shader file) so they don't make Unity compile unnecesary variants.
Volumetric Fog & Mist goes a step further and includes a Build Options section in the inspector that allows you to disable many shader features/keywords with a click so you don't have to edit the shader files by yourself. So this should not be an issue if you make proper use of the asset.
Other shaders on the Asset Store that use keywords and also the new Unity PostProcessing stack will produce same issues (lengthy compilations and lot of unused variants included in your build) unless you manually edit the shader source to comment out the unwanted keywords.
Shader Control is a useful package on the Asset Store that quickly locates all shader keywords in your project, list them by shader and allows you to disable any keyword with a single click.
In any case it's recommended to read the documentation of the purchased packages which probably covers this issue.
AFAIK Unity 5.6 brings some improvements and optimisations during the shader compilation stage so it should help as well when it comes out.

 

Confirmed!
After adding Unity PostProcessing BETA, building was 'stuck' at packaging resources. I didn't bother waiting and seeing when it will unlock, though. Just deleted the newly added files and we're good to go again.

Also, confirmed that any standalone, xcode project and linux builds (we can safely assume others would 'fail' too) didn't complete.

Hope this helps.

 

I upgraded my project to 5.6.0b8. After I was unable to get system to "settle down" (auto bake delays), I disabled Baked GI and Realtime GI and did a manual bake. (Large project, so took 2 hours). Then I tried a build and found that Thrawn75 above is correct, the first build takes very long (mine took almost 2 hours) but then it gets better...ie probably the variants issue.) It appears to hang during the build, but it does complete eventually. Note: I work on a linux ubuntu machine with 16gb Ram and was able to create linux, mac and windows builds successfully. Also, for the record I used Gaia & Aquas in this project.
Update: Certain areas of the underwater Caustic in Aquas did not bake at all, so not sure what the problem is yet...
Next, I re-enabled Baked GI and Realtime GI (you must decide if your project needs it), and did a new manual bake, then build.

 

The error may also appear if your hard drive is full...

 

I went to Window --> Lighting --> Settings and scrolled down and hit Generate Lightmap at the bottom on the first tab of the lighting window. It creates a folder for the scene. I had been messing around with Lighting earlier and doing this fixed it.
I had also been using Post Processing for the first time and have determined that was not causing the issue.

 

I've been having this problem and apparently Unity doesn't catch when it runs out of memory, if you have ample RAM you can open task manager, right click the Unity process and select "go to details" then right click that and set priority > high to give it more memory to work with. This works for me sometimes but not 100%

 

I'm having this problem in Unity 2017.1 too! But the fixes suggested here didn't work...

 

In my case, It was bloom effect which froze unity, also in the build settings I unchecked the auto graphics API and removed Vulkan and open GLES.2 it does take some amount of time to build after adding the Effects to build.

 

#2, #13, and #16 saved the day for me. Using Unity 2017.2.0f3.

 

in my case it solved by removing "uber shaders" which comes with unity "post processing stack" asset

 

In my case it helped when in Edit/Project Settings/Graphics in always included shaders i included the shaders i used in my build

 

In my case it was a Prime31 plugin issue, they have released an update to fix it

http://support.prime31.com/29197/prime31-and-unity-2017?show=29197#q29197

 

Just ran into this. I had to delete the "Postprocessing" folder that was imported when I was playing around with the post processing stack. Didn't end up wanting to use any of it anyway.

 

My build also freezes on packaging sharedassets0.assets..
Previous builds were all going fine.. Then suddenly the build started to freeze on sharedassets0..
I didnt make any changes in the project , so what may be the problem ???
Please help me ...
Thank you ..

 

Got the same problem as ShardulMane... im only using Standard shader in my project and when using it i cant build my app.

 

just remove the buildin standard shader from always include. It will build fine.

 

You can also exclude manually some compile branches from PostProcessing/Resources/Shaders/Uber.shader :
For example, if you don't need Chromatic Aberration effect, replace :

Code (CSharp):

1. #pragma multi_compile __ CHROMATIC_ABERRATION

by

Code (CSharp):

1. #define CHROMATIC_ABERRATION 0

I think that UNITY_COLORSPACE_GAMMA should not be disabled.

 

Building for mac the first time it took around 15 minutes when a build usually only takes me 4-5. But it pushed through it fine.

 

All of the above does not have the answer I want !!!!!!~~~

 

In my case unchecking on the Terrain 3D object "LightMap static" option fixed it.

 

Same problem here.
Trying solutions posted on this forum to see how far I can get.

Update: Fixed by removing PostProcessing free asset from unity

 

I think that if you only need Bloom effect, you can simply disable the ones that you don't need, This answer did work for me my compile time is now 4 - 5 mins without deleting the entire post processing folder. Thanks @Melcx !

 

This works for me although I don't really understand why. I noticed my compile worked first thing in the morning, but never afterward. So I checked out the performance metrics in the task manager. When the pc boots up the core memory usage was definitely the smallest. As you run more apps it goes up. So every time I want to do a Android compile I shut down the computer, boot it back up, and immediately compile my game. The core memory usage goes down from over 6 mb to just under 4. It always works. Maybe the Android compile needs more memory but doesn't want to tell you that or crash when it goes into an infinite loop. Sometimes when the memory usage is low, under 4 mb it still doesn't work unless I shut down the computer and compile right away when I start up the computer. I tried changing the shaders but that didn't fix the problem. It may help the game run better. It's always good to learn. I learned about the mobile shaders. They look almost the same but should help performance when running. This technique always works for me. I would be hopelessly stuck without this technique. Hope this helps.

 

As someone pointed, in my case it was the lack of space in C:, despite the project was in G:

 

If you have this problem when you imported postprocessing effects, try this solution but only add post processing effects shaders. This solved the problem for me.

 

Thanks MarshCZA ,setting set priority > high to Unity process in Taskmanager solved my problem.can anyone help me in suggesting nice article on APK build process

 

in my case
Post Processing Stack
cause this problem when i remove this build working fine .

 

and me too thanks for all your answers

 

Thanks, that is my problem lol.