Hidden nested instances are not receiving updates

Update in case this helps anyone: My team has decided to try publishing all atoms, but put them inside of a black colored section. This causes them to show up in the assets panel with a black background to indicate that they are just helper components that the team should not directly use.

Having this problem as well. Commenting to bump the topic. This is a huge problem, I think what we need is a convention for hiding from publishing and hiding from the asset panel.
maybe _hides the component from asset panel

.does not publish the component

Commenting to also keep this topic alive. Crazy that there has been no meaningful updates that so many of us imply was an oversight. It is crazy to think that we’d want to publish every single little thing and not nest and control the behavior of certain components. Figma, please help fix this! It’s becoming a pain for many.

Absolutely needed.

Adding my voice to this. It's been over a year, and this remains a significant point of friction for any team managing a mature design system.

Hey @Figma, it's clear people are waiting. Any chance of an update on this bug?

Hey ​@Denis24, thanks for chiming in here! 

To clarify again, this is currently expected behavior for hidden nested instances.
I’ve updated this topic into a feature request, and we’ll flag the feedback here to our team for future consideration. 

Bumping up the topic. We desperately need back function to hide components from the “Assets” view but still be able to publish & update them as they are used as instances within more complex components…

In the past we used “_” to hide “templates” that are used within more complex component’s but some time ago it completely broke, components are completely hidden and are unusable within main component…

What is the purpose of having a component inside library that is not usable outside the library…? It was main use case for “_”.. To hide it in “asset” view so designers are not able to use those “templates” outside the designated main component they were made for..

It’s been more than a year since people started reporting this “bug fix” as a cause of a real problem. Where can we expect to fix it and bring back proper functionality?

I have reported that is as a bug as well. I working through a bootcamp that uses figma, and I am experiencing this behavior now and it is the most infuriating obscene bug  I have come across in a top shelf software company.  Saving an accurate version of what you produce should be rudimentary behavior. This bug essentially means that there is some kind of hidden trick to saving files and if you don’t know how to do it you’re screwed. I have spent the last week and a half fighting with the software.  Filed bug reports, with responses telling me to use “Regenerate Component”  and “Save Current Version” and always the same behavior. If you make a component (an Accordion)  that has sub components (Accordion Items) and you want to use it multiple times in a projet your screwed if the contents of the sub components needs to change. It will only take the data of the initial component creation.   How have designers used this software like this for so long? I spent 18 years as a software engineer, and I don’t know how this software got so popular with  designers if the software it is this dodgy . 

How can this be expected behaviour when users who use Figma on a daily basis would expect, and even desire, different behaviour? Please resolve this, as it is extremely time-consuming to expand components in this way. 

i wonder if any user has EVER used the hide feature the way figma claims it should be used. it’s inconsistent and crippling to us.

hidden variables get updated (THANK GOD)
but your hidden component? you’re SOL.
and now with slots it’s even more egregious