Skip to main content
Solved

Resolved: Overrides not preserved when library is pushed


Show first post
This topic has been closed for comments

153 replies

Josh
  • Former Community Manager
  • 1019 replies
  • January 20, 2022

Alright thanks everyone for your reports. We believe we’ve found the core issue now. The team is still actively investigating and will be working on a fix. I’ll be sure to update this thread as I have more info.


Vasil_Tiholov

Thanks but this is a sort of an issue that should just never happen!

There are tons of perfectionists doing UI design here that want to have complete control over every single piece of the product they are designing.

This seriously undermines how much I trust the product to give me that certainty.


Vasil_Tiholov

Will it be possible for my Figma files to be reverted to a version of yesterday? 19 January 2022?


Hugo_Figueira

Yes, you can go to File > Show Version History and then select the one you want.


Vasil_Tiholov

Yes but the thing is that when this issue occurred, I replaced my files with my backup files and now I do not have the original files on Figma.


Josh
  • Former Community Manager
  • 1019 replies
  • January 20, 2022

Hey @Vasil_Tiholov thanks for reaching out and sharing this feedback. I totally understand your frustration here. With any type of incident like this (big or small) our team always makes sure to look into what exactly happened and how to make sure it doesn’t happen again.

As I get more information on this issue, I’ll be sure to update this topic. For your specific case I would recommend reaching out directly to our support team (support@figma.com) so they can look closer into it.

Thanks


Naga
  • 1 reply
  • January 20, 2022

@Josh If you need any help to understand. I can help you over a call. This has created a lot of issues now 😦


Vasil_Tiholov

Just wrote an email. Hope help arrives quickly as I cannot proceed working at this point…


MorganeUI
  • 1 reply
  • January 20, 2022

Même problème ici, nous avons des librairies communes, dès lors qu’on pousse des mises à jour, tous nos textes disparaissent…


luiscamino

oh “thank god” it’s not just my problem, but what a frightening thing to be happening!! the component that is resetting overrides for our hundreds of files is the “headline” which is used on top of every screen to describe the name of a screen or anything. basically every title on every file is resetting itself to “Title” and it’s giving me a heart attack 😖 restoring to older versions doesn’t help, it still triggers a reset of text.


Thor
  • 2 replies
  • January 20, 2022

Has this issue been resolved? I was getting a update for a component that was resetting all overrides to defaults, but now it seems to have stopped.


Wawrzyniec_Wroblewski

Is there any recommendation on how to handle this? I want to avoid losing 2 days of work and spending a few more on updating components in all interconnected libraries.
I assume that I should restore some previous versions on all affected files but I can’t see any info about when the Figma update was made so literally I’m stuck.

I would appreciate any suggestion on that.


Mattias_Berkesten1

I would also like to get some feedback from the support team if all overrides that now is lost can come back or not. If not as some previous members have written there is a lot of hours that has vanished and this might then be the largest incident due to its impact.


Antoine
  • 144 replies
  • January 20, 2022

Same here (I think?).
I updated descriptions on certain base components in my library file. After publishing and pushing changes to a file using these components, I found that any text override had been reverted back to default. I think it’s the same bug but not entirely sure as I haven’t really studied the impact of updating descriptions before.


Brendan_Tobin

Same here. I wonder when we can expect a fix. Really impacting ongoing work here


Dmytro2
  • 2 replies
  • January 20, 2022

I have the same issue. Does anyone know how to solve this? Otherwise, our team is going to lose months of work.


Jean-Marc_Lehwald

I am really speechless. How can something like this happen? And why can’t you put an old version on production and take care of the problem in a staging environment?

@Josh we are a team of more than 30 people and we all can’t work. The developers can’t import. Everything is at a standstill.

That really speaks all against figma right now — that they haven’t had a solution to the problem for hours. How can we ever trust the software again?

The company I work for pays a lot of money for licenses. And there is no official statement about the current status from figma.


Vanden_Meerssche_Wendy

I’m having the same problem. When publishing my library, all text overrides are reset and prototype links are deleted.


Asseco
  • 1 reply
  • January 20, 2022

@anon21722796 Please fix this issue for the sake of all Figma users!


Josh
  • Former Community Manager
  • 1019 replies
  • January 20, 2022

@Jean-Marc_Lehwald Thanks for reaching out and sharing. I totally hear you and understand your frustration. We’ve been working on trying to identify the core issue so that we can properly roll-back/fix, which we finally did. We’re working on deploying a fix now and will keep everyone update here and via status.figma.com


Abertran
  • 1 reply
  • January 20, 2022

Same here… Hope the fix will come soon. Lots of hours lost.


Vasil_Tiholov

I know that this may not be as helpful as it should but I do manual backups of all my Figma files daily. I download the files and upload them to Google Drive. This way I have a place where I store older versions of our product designs.

In today’s situation, this has helped me with being able to upload the backup files on Figma so our developers can keep working.

Besides from that, I’m waiting like everyone else for a fix so I can also resume my work… 😕


Wawrzyniec_Wroblewski

If the versioning worked as intended there would be no need to do it. If someone had the same impression about this feature please upvote this → Version history not working as intended


Vasil_Tiholov

Yeah, of course.

It’s just that I never felt I can fully trust how files communicate with each other and whether if I roll back to an older version things are gonna sync properly.

But you are right. It should work without manual stuff like that. 👍


Jean-Marc_Lehwald

Tried again und it worked for two releases, but not for the other ones. But its a first sign, after waiting for 12hours 🍸


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