Instance swap issue. Height set to fixed

Hey Pablo, thank you for reaching out with a screen recoding and a link to your file. This looks like a bug to me. I’ve created a support ticket on your behalf, so that our technical quality team can take a look at this. Your ticket number is #849291, for reference.

I keep having this same issue, @Gayani_S Has it been fixed?

Hey @Fayemi_David ,
I am working closely with Gayani, happy to help!
After checking internally, unfortunately we cannot set an ETA yet for the fix for the instance swap issue at this time. Still, once we have an update I will let you know. Thank you for your patience in the meantime.

I have the same issue with a different component: A side menu.
When I swap between a selected state - with sub-pages below - to any other state and then swap back to ‘selected’ the component’s height changes to fixed instead of its preset ‘hug’, cropping the content (sub-pages) below.
Any update about this 7 months later?

Same here. Instance swapping doesn’t seem to respect the intrinsic size of the component that is swapped to. If the sizing is set to “Fixed”, it holds on to the intrinsic size of the component instance that is defined as the instance inside the main component.

Any update on this topic? Like this there is no advantage of using instant swaps when the components have wrong sizings.

I have this exact same issue and have no idea how to fix it.

@Gayani_S I have a similar issue which is also happening when I swap a variant nested in my component also. The strange thing is, its is not consistent across the nested variations within the component.

I have a component with two mockups, their position and scale are the variations.
Inside the mockups are nested variations, allowing me to swap the mockup screens.
The bug seems to only happen with the mockup position which has had its scale adjusted in the final component.

Please see the video below, comparing the same component but the bug showing on the scaled down component.

I am hoping it has to do with the way I’ve built the component rather than a bug that has an undefined fix time as I am close to a deadline for a client!

Hey @Jahren, apologies for the delayed response!
I’d also comment to double check this with the support team. I saw that you’ve filed a ticket with our support team (#1068249) but you have got any response yet. Please be aware that we are facing increased contact that’s why there is a delay.
I am going to escalate this internally with the teams, so you get help asap. Please also provide a direct link to the file, and invite support-share@figma.com with “can edit” permission so our team look into this further. Note that users with @figma.com emails on your team do not count towards your billing.

Thank you!

I am also having this issue. Just spent forever trying to figure out what I was doing wrong.

Hey @Savannah_Niemeyer, thanks for chiming in!

The team believes this is related to long-standing issues with using scale on nested instances, so we sincerely apologize for the trouble this is causing.

As a workaround, if you have used scale on your instances, instead we recommend manually making overrides to the instance size and setting constraints to help the nested content scale accordingly, as these overrides should be reliably applied when changing states in situations where you see the scale override does not function as expected.

@dvaliao Does this mean the team will be working on a fix some time soon, or given it’s a long-standing issue, they have no idea how to fix it yet?

Hey @Ara_Garabedian,

Unfortunately, we can’t guarantee a specific timeline for the fix. The team has not yet been able to find a good solution. The trickiest part for most of our long-standing bugs being how best fix without introducing other performance issues.

faced this today. 10 months and still it is not fixed! Such a common issue

This issue still present as of 125.1.5

When can we expect a fix?