Skip to main content

Hello everyone,

since yesterday, weird library updates have been showing up in almost all of my files. They show updates that supposedly have been published months ago (some up to 4 months). Those are libraries I use and update almost daily, so I’m confused that they offer updates from months ago now.

When I click on “Update”, Figma quickly says “Successfully updated assets”, but nothing changes.

When I click on an icon to see the side by side comparison, it loads forever.

I tried to force another update from those libraries to see what happens. Now the Base Colors library says “Published 1 day ago”, but the problem remains. It won’t go away. 

I also tried doing the “Reset Figma and restart”, which I think formerly used to be “Clear cache”. And I obviously restarted the computer, but nothing helps.

Anybody have any idea what else I could try?

 I had the same situation on Monday, and it's still the same today. 😕🤷🏻


Hi everyone, thanks for flagging this! This looks definitely odd.

As a temporary solution, please:

  • Try first to clear your cache on the desktop app and/or in the browser
  • Un-publishing your library (your subscribed files will not lose any connections)
  • Refresh / reload the file
  • Publish your library again

You can clear the desktop app cache:
On a Mac in the Help menu under Troubleshooting. If you'd prefer to manually clear your cache you can:

  1. Quit the Figma desktop app
  2. Open Terminal.app and enter the following command: rm -rf "$HOME/Library/Application Support/Figma"
  3. Try opening the desktop app again

 
On Windows under the toggle-arrow at the right of the top toolbar under Help > Troubleshooting. If you'd prefer to manually clear your cache you can:

  1. Close the Figma desktop app
  2. Open the Start menu, and paste in this, followed by enter: %APPDATA%\Figma
  3. In the window that opens, delete the Desktop and DesktopProfile folders if they exist
  4. Launch the desktop app again

 

 If the issue still persists, please reach out directly to the support team so they can take a closer look here: Submit a bug report

In the form, please include a direct link to the library file and grant edit access to support-share@figma.com so the team can investigate it— this won’t impact your billing in any way. Thank you!
 


Hi ​@Miriam7 ​@Bill_Chen 

 

Thanks for your patience! This is Toku from the Figma community team - working closely with Céline.

Our engineering team confirmed this was a problem on our end and they've shipped a fix. Could you try publish the current pending updates first? The issue should be resolved, but if you're still running into any problems, please let me know and I'll help get it sorted.

Really appreciate your patience while we got this fixed!

 

Thanks,

Toku


Hello, sorry for not getting back to this before, the support suggested to remove the library from the file and add it back into it, and it worked (re-opening file before moving library back in). 

Best regards!


Hey ​@Miriam7, glad to hear it’s working now, and thanks for sharing the solution with the community! I’ve marked your reply as the ‘Best Answer’ to help others find it more easily.
Thank you


Hello, sorry for not getting back to this before, the support suggested to remove the library from the file and add it back into it, and it worked (re-opening file before moving library back in). 

Best regards!

I’m facing this issue as of today 30-06-2025, and I tried all the suggestions listed, even this one of removing and re-adding the library to the file (re-opening file before moving library back in).

But the problem still persists. 

I have emailed support@figma.com now. Looing forward to a permanent fix.


Hi ​@Michelle6 , glad to see the issue is now resolved on your end!
For anyone else experiencing something similar: our engineering team has pushed a fix. To apply it, please:

  • Refresh Figma
  • Publish any pending updates on the main library
  • Apply any updates on the subscriber files
  • Wait a few minutes

If the issue still persists, please submit a bug report directly so our team can investigate it further with your case. Thank you 🙏🏼


Reply