just in case, reporting here too, that bug is still there @Figma_Support

I can’t believe this bug still exists after config. Super annoying! I’ve had this for months @Figma_Support

@Figma_Support 🤔

@Figma_Support

One year later @Figma_Support and this is still a major problem

2024 and still the bug

Hey there

I noticed a similar problem on our project, when I tried to detect the root of the problem, I noticed that one of our teammates had done something wrong.

that was it: the whole auto layout was set to “Hug content” and on the other hand, the component inside of it were set to “Fill container”, so Figma couldn’t see the proper logic to calculate. To fix this, you just need to change of them.

generally Figma changes one of them, according to the last change to prevent this bug, but sometimes it goes wrong and runs to a bug.

I guess it will solve your problem too, and there will be no more jumpy-jumpy auto layouts or components or text layers 😉

cheers

The bug is still very much there and I have had some minor problem the last year or so with this. However since the last month or two the bug has become so bad that it is everywhere right now and almost every component I update now gets affected by this.

Another problem with this bug is when I as a designer double click on it, it disappears and solves itself however the dev team still sees the original bug.

EDIT: after a lot of searching around here I found the following solution that seems to work for me by using the“Regenerate all instances (slow)” command from the Quick Actions panel. However this seems to only apply for a specific page and not the entire project so you will have to do it page by page.