Skip to main content
Solved

Deleting text property in master component resets text in it's instances


Julia_Mnizhek

Hi!
Has anyone encountered this issue: some of our components had text properties so the text could be set directly in the properties panel. Some time later, we decided to delete these text properties. As a result, after publishing the library, in all instances of SOME components (not all, SOME), the text that was linked to the variable gets reset to the default. 

But this doesn’t happen in every component that had a deleted text variable.

Is this a bug or expected behavior? Has anyone run into this? How did you deal with it?

We have a large library used by 50+ designers, and what seemed like a tiny update that didn’t break anything during testing ended up resetting values to defaults in some components after publishing.

 

Best answer by Julia_Mnizhek

Writing this for anyone else dealing with big, messy libraries and running into the same kind of issue. Here’s how we ended up fixing it:

  • We restored the library file back to a version before the breaking commit, published that, and the buggy commit disappeared from designers’ commit history (though it’s still in the file’s version history). After that, everyone could safely accept library updates, text overrides in components weren’t reset to default. We also decided not to mess with text props at all for now, since there are similar Figma bugs popping up.
  • In some old files or with old components, we used “Restore component connections” before accepting updates from the library. If we didn’t, the texts would still reset.

The frustrating part: Figma support spent a month going in circles and never gave us a proper fix. We could’ve solved this way earlier. Super disappointed with the support experience, and to top it off, the feedback form at the end wouldn’t even let me submit a comment.

View original

4 replies

  • Figmate
  • 2002 replies
  • April 15, 2025

Hi ​@Julia_Mnizhek, Thanks for letting us know about this!

 

I understand you're experiencing an issue where overrides you've made to text properties reset to the default when those properties are removed from the main component.

 

It looks like you've found a long-standing bug that our engineering team is working on. Unfortunately, we can't give you an exact timeframe for when this will be fixed, but we appreciate you bringing this to our attention.

To help in any small way I can, I've added your post to the existing report to help get this issue more attention and hopefully move it up the priority list.

 

Thanks again for contacting us!


Julia_Mnizhek
  • Author
  • New Participant
  • 18 replies
  • April 15, 2025

Thank you ​@Junko3  for the reply! And thank you for passing this on to the engineering team. It helped clarify things a bit. I’m currently discussing this issue with support, but they haven’t given a clear answer yet. Hopefully this bug gets fixed. Looking forward to it.


Julia_Mnizhek
  • Author
  • New Participant
  • 18 replies
  • Answer
  • June 5, 2025

Writing this for anyone else dealing with big, messy libraries and running into the same kind of issue. Here’s how we ended up fixing it:

  • We restored the library file back to a version before the breaking commit, published that, and the buggy commit disappeared from designers’ commit history (though it’s still in the file’s version history). After that, everyone could safely accept library updates, text overrides in components weren’t reset to default. We also decided not to mess with text props at all for now, since there are similar Figma bugs popping up.
  • In some old files or with old components, we used “Restore component connections” before accepting updates from the library. If we didn’t, the texts would still reset.

The frustrating part: Figma support spent a month going in circles and never gave us a proper fix. We could’ve solved this way earlier. Super disappointed with the support experience, and to top it off, the feedback form at the end wouldn’t even let me submit a comment.


Celine_
Figmate
  • Community Support
  • 3576 replies
  • June 5, 2025

Hi Julia_Mnizhek! Celine here, working closely with Junko.

Thanks a lot for sharing this detailed workaround — it’s super valuable for others who might be navigating similar challenges with large or complex libraries. I’ve gone ahead to mark as ‘Best Answer’ for this topic.

Sorry to hear about the frustrating support experience and the issue with the feedback form — We’ll share this with our team, and we really appreciate you taking the time to share your thoughts.
I’ve gone ahead to create a new support ticket for you, feel free to check your inbox (your email address linked to your Figma account  - jxxxk@sxxxxh.com) when you have a moment to share your comments. For reference, your ticket number is 1382263.

Hopefully your post helps others avoid running into the same issue. Thanks for bringing this up!


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings