Skip to main content
Solved

Library with pending changes to publish

  • February 24, 2025
  • 2 replies
  • 73 views

Tanya_Cedillo_Quiroz

I clicked on publish updates as usual, but this time the updating process didn’t start. I waited like 5 min. and nothing happened so I closed the file and opened it again, and there was a badge saying: “This file has unsaved changes”. I tried to publish again but it didn’t work. All these is happening only on the Figma app, because I opened the file in Chrome and I successfully published the changes from there, but if I open the file on the FIgma app is still showing the badge of pending changes (and a little blue icon to sync in the thumbnail view). 

This is the second time this has happened in different files. 
The previous one I duplicated the file from Chrome with the final updates applied and then removed the old file with the pending changes, but is not the ideal, since I needed to sync that “new/duplicated” library and relink it into the design files. 

 

 

Best answer by djv

Hey ​@Tanya_Cedillo_Quiroz, thanks for reaching out! 

Glad to hear that your changes were able to be saved from the browser. After syncing the changes on the browser and returning to the desktop app, did you try refreshing your open file tab?

Have you checked that your desktop app is up to date? If you’re refreshed your open tab and your desktop app is up to date, can you also try clearing your desktop app’s cache?

View original

2 replies

djv
Figmate
  • Community Support
  • 4798 replies
  • Answer
  • February 24, 2025

Hey ​@Tanya_Cedillo_Quiroz, thanks for reaching out! 

Glad to hear that your changes were able to be saved from the browser. After syncing the changes on the browser and returning to the desktop app, did you try refreshing your open file tab?

Have you checked that your desktop app is up to date? If you’re refreshed your open tab and your desktop app is up to date, can you also try clearing your desktop app’s cache?


Tanya_Cedillo_Quiroz

Hey, thanks for the quick answer!

My desktop app is up to date, but what solved the problem was cleaning the cache. Thanks a lot! :) 


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