I have several components in my library that share the same problem.
When I change properties on an instance of the component, sometimes it resetts the text. Then I undo, and change the same property again, and now the text isn’t resetted anymore.
Since it only occurs randomly, and after undoing it works properly, it looks like a bug to me. But maybe someone elese had the same problem?
Hey Magdalena, could you share a screen recording with us when this is happening?
Here’s the video of the problem: https://clipchamp.com/watch/e2H6hL3NYqZ
It shows that after I first change the variant of the component the text resets to default, then I undo the change, then change again and the text is not resetted anymore.
And below is the screenshot of how the component is build. I know it’s far from perfect, but it’s been created ages ago. Can you see anything what can cause a problem in here?
First I thought it is because there are nested components which are not published, but after I have published them the problem still existed.
Thanks for sharing! I’ve just created a support ticket on your behalf, please share a link to the file with them. Your ticket number is #851340, for reference.
I got here by search because I have similar problem. Text property values in my nested components get reset to defaults at random and the desktop app crashes. Is this some known issue? If it keeps happening I guess it hasn’t been resolved yet
Hi everyone,
We’ve discovered a significant bug in Figma. When modifying a nested component within a main component, the text values become disconnected in all instances where the main component is used.
Details:
In the attached video and link, we’ve recreated the issue with a simple structure:
When we change the text content on the page and then edit the main component, the labels do not update accordingly.
Please refer to the attached video for a demonstration. Link to the Figma file: Bug Report
Thank you!
Hey Walicki
We are currently experiencing a similar issue and my colleague just made a post about it here: Major nested component bug
Is your issue the same? Did you find a solution?
Hey Bart,
My problem is similar to the one your colleague posted, but a bit more complex. I have multi-level nested components, the instances of which lose the overrides in the text properties and revert to the defaults in the main component. I haven’t found a solution yet.
BRgds, Piotr
I’m watching the topic as I too am affected. Text properties in my nested components are getting reset to defaults completely at random and even explicit version saving does not help.
Hey everyone, apologies for the delayed response! Thank you @Sanny for sharing a screen recording with me.
Can you both let me know if this is happening in the browser and the desktop app?
And can you please try the following steps to see if this resolves your issue:
→ Go to the main component
→ Open the quick actions menu (press command /)
→ Run the commands “fix instance overrides”, “repair component connections” and “regenerate all instances (slow)” on the main components
→ Publish the update of the main components
→ Accept the updates in the instances
Please let me know if this resolves the issue, happy to help out further is it doesn’t.
Hi Gayani, thank you for your reply
Please find my comments below:
Can you both let me know if this is happening in the browser and the desktop app?
I don’t use the browser version.
→ Open the quick actions menu (press command /)
Cmd + , on my keyboard layout it is
→ Run the commands “fix instance overrides”, “repair component connections” and “regenerate all instances (slow)” on the main components
Searching for “fix instance overrides” in Quick Actions finds nothing. "Repair component connections works, but only temporarily. That is, after closing and reopening the file, all text properties in instances go back to defaults.
BRgds
Piotr
Hey @Walicki_Piotr, thank you for confirming this!
I’ve just created a support ticket on your behalf. Your ticket number is #1094852, for reference. Please download Figma desktop app debug logs and share it with the team.
Our support team usually takes up to 24 hours to reply back to emails - tends to be quicker than that in normal circumstances. However, please be aware that we are facing increased contact volume so there might be a delay.
Appreciate your patience in the meantime!
Hey,
Thank you for replying. I’m currently on Holiday, when I’m working again I will test it first thing.
Cheers
Hey @Sanny, no worries! Enjoy your holiday and feel free to get back to me when you’re back.
Thanks,
Gayani
Hey @Gayani_S ,
I’m back.
I’ve investigated the issue, but none of the suggested solutions have resolved it.
This bug is a major problem for our agency. We rely heavily on component libraries across all our projects to save time and maintain financial stability. Starting from scratch with every component isn’t feasible.
Component-based systems are essential for designing digital products, and having to manually update each instance whenever a component changes is incredibly inefficient.
We hope the product team prioritizes fixing this bug, as it’s directly impacting our profit margins in our industry.
Cheers,
Sanny
@Sanny - stepping in for @Gayani_S to assist. I did some digging and saw you actually wrote into support regarding this. One of our agents last sent you a response on 8/13 letting you know that they weren’t able to replicate the bug you reported, and requested a screen recording of the behavior you are seeing.
Did you not receive this email? If so, let me know and I can get the conversation going again – hashing out this problem will need to be continued via email, since it may require more details about your design work (and we want to keep that private to yourself and support).
Hi,
Thanks for stepping in to assist. I was on summer holiday, so I might have missed that email. However, I’m now back and in contact with the support team via email. We’ll continue the discussion there to resolve the issue.
Thanks for the follow-up!