Latest Figma update broke my components

I have the same problem after the latest update.

We have the same issues. This must be fixed. Border and fills are flickering when smart animate is used in the prototype on a hover.

This is effecting me as well – noticed it yesterday. This was NOT happening late last week as I was working on the same prototype and these problems didn’t happen.

Smart animate prototype shows a gray overlay/flicker during smart animation transitions, but only when I’m logged into my account. If I make the prototype available to anyone and I view it with another Figma account it does not happen. See image.

I’ve verified this is an account issue as it happens on multiple browsers and computers. This is also happening  across all of my past files that use smart animation transitions. I’m guessing this is effecting accounts in experiments or rollouts affecting the prototype player.

This basically makes prototyping with smart animate useless as it’s incredibly distracting.

Hey Adam,

Yes, that’s exactly the issue. I hope the Figma team can fix this quick!

Same here… happens on all prototypes on our team’s account. Any component with interactivity is affected.

Same issue is happening for my files. Right before a presentation 🤦

Figma needs to fix this ASAP.

Sorry to hear that! Hope the meeting goes your way 👍

Got this from Figma support – looks like it should be solved.

--

This is Clara from Figma Support. Thank you for reaching out and sharing this helpful example!
 
We apologize for the inconvenience. Our engineering team has investigated this further and we identified a recent change on our end that was causing this unexpected behaviour for some interactions.
 
We just released a fix, and I'm no longer able to reproduce the flashing behaviour expanding the sections in the prototype you shared here

Hey All, thanks for flagging this! 

As ​​​​@Adam Tolman mentioned, our team investigated this issue and were able to push a fix. Please refresh your tabs and let us know if you run into any further issues. 

Hey djv,

Thanks, the issue is solved. 

Thanks for confirming, ​@Zé Casal! 

Glad to hear. 😊

In our team it keeps happening, but with hovers in prototypes. Components we’ve been using this year that worked perfectly are showing hidden boolean items on hover and once you leave it keeps the booleans active. 

Hi ​@Frida Ae, sorry to hear this! 

When was the last time you refreshed your tabs? And are you using the latest version of Figma (125.10.8)?

The fix we pushed yesterday should have also fixed issues with hovers. Are you able to share a screen recording of what you’re seeing on your end? 

With more information, we can send this back to the team to investigate. 

Hi Figma Team,

This issue is still not resolved.

When we update a component and publish changes from our design system file, the updated icon in the main design file resets to the default icon.

Example:
If we replace the component’s edit icon with a three-dot icon and make color changes, then publish the component, everything looks correct in the design system file. However, after updating the main design file, the three-dot icon reverts back to the edit icon.

Please help us resolve this issue.

Thank you.

Hey ​@Ravi Saxena , Celine from Figma here. I am working closely with ​@djv , happy to assist.
Thanks for following up and for sharing the details. As you are still having issues, to help us investigate this further, I’m going to send you a DM to gather some important information so our team can take a closer look at what’s happening. Please keep an eye out for my message. Thank you!
 

Hello Figma Team, 

I am unsure if this is part of the same issue, but, I have been facing this with the toggle component, when trying to add different interactions for the different variants (States - Default, Hover, Disabled). 

When hovering, the default changes to hover variant (this interaction is at the Parent component level) and at the instance, on hover I added a click interaction with a conditional action. (Bear in mind this is all for when the Toggle state is off). 

Now when I try to add a click interaction for Hover (when Toggle State is On), I see that the Hover (Off) click interaction is visible. This is weird. 

It seems as if the interaction is not getting applied to the state/variant but on the entire component. Not sure. 

As this behavior I am seeing post the update and not before.

Can you assist? 

Hi ​@Hrishikesh Iyer , thanks for the detailed explanation, that’s really helpful. From what you’re describing, this does sound like it could be a different issue, and it’s something we’d need to take a closer look at directly in the file to understand how the interactions are being applied at the component vs. variant level, especially if this behavior started after a recent update.

To investigate this properly, the best next step is to reach out to our support team so they can review your file in detail.

You can do that via our Support Hub here:

1. Go to the Support Hub

2. Type your question

3. Click Start Chat, and type ‘Report a bug’ .The chatbot will help you open an email case with our Support team.

Once you’ve submitted the request, the team will be able to dig into the file and follow up with more specific guidance. Thanks again for flagging this!

Today I have run into an issue that seems related to what was reported by Frida Ae. My component library is 2 years old and everything worked well up until now.

Currently however, when hovering over certain components in my prototypes they appear broken. It seems more or less random which components are affected. Some of the components change to states they should not, the label-text is lost while hovering or they randomly show elements like labels, helper text or icons that should not be visible per the defined boolean settings .This has not happened before. There were no updates made to the library in the past months that could be the reason for this behaivour.

What can I do to fix this? ​@Celine_ 

Hey @David_Ortner,  thanks for flagging this and sorry to hear you’re running into issues with your components as well.

Without looking directly at the file, it’s hard to determine the root cause. Since the issue originally reported by Frida dates back about a month and we didn’t receive further updates at the time — and given that it seems to have been resolved for some users — it would be helpful for our Support team to take a closer look at your specific case.

For anyone else still experiencing this issue, please submit a bug report so the team can investigate further and better understand what’s happening.

Please follow the steps I mentioned to reach out to our support team via the Support Hub here:

1. Go to the Support Hub

2. Type your question

3. Click Start Chat, and type ‘Report a bug’ .The chatbot will help you open an email case with our Support team.

Thanks for your help! 🙏🏼

Update: For Ravi Saxena’s issue, I can see in the backend that it has been resolved on our side. Sharing the the temporary solution here in case it’s helpful for others: ‘Open your Actions menu in the file you're pasting to, using the keyboard shortcut Cmd or Ctrl + K, and typing "regenerate all instances slow," and hit enter.’