Bug when switching variable modes in nested components

It looks like an error in the assignment of variables, in my file the text is switched automatically, because its size is embedded in the token, and the token is not connected to propertes, but to numeric values (height, text size, etc.).

Good afternoon, can you tell me when the problem will be solved? Many people are waiting for this bug to be fixed

Having a related issue with modes and variables, if a nested component is set to a different mode to the parent component then the variable doesn’t change when clicking on interactions (eg. I have a counter that should go up by 1 every time I click a button but the counter stays at 0)

Switching the nested component to ‘auto’ or manually setting it to the same mode fixes this.

Took me ages to figure out what was wrong as I had mass set the mode on a bunch of screens yesterday and didn’t think there would be a connection to the issue.

Hi @Alexey_Kolesnikov, I’ve also had this issue and found the command (CMD+/) “Regenerate all instances” can sometimes help fix disappearing content without having to unlink the variable from the prop.

Thank you, it really is faster

I have a component with 2 different nested components (a logo and a currency symbol).

The nested components have 3 variants each. Which variant is shown is determined by a variable mode.

When the parent component is placed on another file, the nested variants disappear till they are clicked on or I use the regenerate.

This occurs whether the parent component is placed directly into a file or if itself is a child component.

The components’ instances in the parent file behave as expected.

Thanks.

I have the same issue, the nested variables for the component variations do not sow when I change them in the instance.

It shows only the “default” variable obtains of the core component variant

I have been having a similar problem.
We have created modes for “tvOS” and “CD”.

We also created a text string to swap components based on mode and applied it to our button component.

The modes swap components and overrides perfectly when in a standalone frame, but breaks down when the same setup is applied to a component.

I also have this issue.

I’m also having this issue.
I have a ‘wireframe’ layout for a component, and then a more detailed ‘mockup’ version with text and images within it. The goal is that I can wireframe a layout, and quickly, when needed, swap to a mockup.
Using a boolean variable seems to work for a few components, but then after applying it to a few components and testing, eventually I start getting blank components, making it appear as if it’s just disappeared when I change the mode of a block.
Then, as I scroll around my file, the others I previously swapped fine, start to disappear as well.
It feels to me like it’s an issue with loading/memory usage.