URGENT: Critical Regression in Component Boolean Properties (Breaking Production Files)

Hey @Michel Kerkmeester , thanks for flagging this, and sorry to hear you’re running into issues with component boolean properties.

I’ve escalated your case internally, and I can see that the team is currently investigating. Please continue the conversation directly through your Support ticket, as they’re best equipped to review the files and assist you further.

Thanks for your patience while the team looks into this! 

Anyone else with this issue? Figma hasn’t been of much help yet.
Our files must be corrupted if nobody else has this issue.

Hey Michel, thanks for the update. I understand why it might feel that way, especially if you’re not seeing others report the same behavior. I just want to reassure you that your case is actively being looked into.

(Our Technical Quality team flagged this to engineering earlier today for further investigation. While they dig into it, your ticket is temporarily on hold, and you’ll be updated directly as soon as we have more information to share.)

Thanks for your patience, we’ll follow up as soon as we learn more.

I’m encountering a high-priority issue with component instances in my files.

Components with Boolean visibility properties, which were manually hidden in my design files, suddenly became visible without any changes to the component library or settings.

The library default is visible, but the instances were intentionally hidden. This has caused a large number of hidden components to unexpectedly appear, significantly impacting ongoing design work.

This issue requires immediate attention. 😢

Thanks for flagging this ​@Zoey , I’m sorry to hear you are also having issue in your active design work.

Since this involves component instances and boolean visibility properties changing unexpectedly, the best next step is for our Support team to review the affected files directly and determine what’s happening.

To help the team investigate, please follow these steps:

• Share edit access to the affected files with support-share@figma.com. This will help our Support and Engineering team to get access to the files for investigation. You won’t be charged for this.

• Submit a help ticket here and include direct URLs to the files you’ve shared, along with a brief description of what changed and when you noticed it.

• Once that’s done, feel free to let me know here and I’ll make sure your ticket is escalated for review.

Thanks for taking the time to report this. I know issues like this can be stressful, and sharing the files will help the team look into it as quickly as possible 🙏🏻

Same here. Unfortunately.

Me and all other designers in my team are having this issue. Hundreds of component boolean states are changing, messing up designs everywhere. Hidden icons are appearing, input fields grow because of hidden labels and helper text appearing, all our prototypes are breaking. This is a serious bug that’s critically affecting our productivity and ability to present designs to customers. This needs an urgent fix!

Hey ​@Tiago_Goncalves ​@Dmitriy Rybtsov , thank you for also flagging it!
Our engineering team is currently investigating it. As mentioned above, additional examples would be helpful for our team.

To help the team investigate, please follow these steps:

• Share edit access to the affected files with support-share@figma.com. This will help our Support and Engineering team to get access to the files for investigation. You won’t be charged for this.

• Submit a help ticket here and include direct URLs to the files you’ve shared, along with a brief description of what changed and when you noticed it.
  
  Once that’s done, feel free to let me know here and I’ll make sure your ticket is escalated for review.

Thanks for your patience while our team investigates! 🙏🏻

Hi again everyone, we've identified a potentially related issue and pushed out a fix.
Can you please reload your tabs/files and let us know if you continue to see the issue happening? Thank you!

Hi ​@Celine_ ,
Thanks for the quick fixes — really appreciate the speed.
I’ve added another ticket for a separate issue.

Glad it’s working now, thanks for confirming!