Skip to main content
Question

Component getting detached upon paste

  • January 29, 2021
  • 6 replies
  • 2813 views

Jung_Lee_ESI

I think this issue has been around for almost 3 years. I love the tool, but this behavior is pretty destructive, especially because you often don’t know why, when, and where it’s happening. So much so that there’s a dedicated plugin to re-attach symbols.

I sounded like there was some type of fix at work, but that was 2019.

Any update?

Spectrum – 13 Jun 18
This topic has been closed for comments

6 replies

Bruno_Figueiredo

Hey @Jung_Lee_ESI 👋

Usually for this to not happen, you have to have your libraries enabled. Is that the case?
Is this happening randomly, or always with the same components?


Gleb
  • Power Member
  • 4707 replies
  • January 29, 2021

What are you copying from where and to where? If you are copying an instance from one file to another, are all components this instance depends on published to the library?

This behavior was improved last summer and now it should mostly happen only when you are doing something a bit wrong. (But could still be some bugs around this, which should be reported to Figma support team via the support request form or support@figma.com.)

Yes, there are plugins like Master that can help you attach instances but if you are copying an instance from a non-published file, for example, it won’t be able to help.


Bhoomika
  • 1 reply
  • August 23, 2022

Hey @Bruno_Figueiredo
This issue happened today and all of our instances(nested or otherwise) were detached without any notifications whatsoever. We published our library today and it was working fine the whole day before this nuisance started showing up out of nowhere. Trying to find a solution online but to no avail. Please help as many flows and prototypes are at stake right now.


Oskar_Schmidt

@Bruno_Figueiredo I have the same issue still. When I copy+paste two instances to another file, they are still instances BUT if I cut+paste them they detach. Is this a “feature” I don’t know about or is it still a bug? Very confusing to have copy+paste and cut+paste as two completely different ways to handle instances.


  • 1 reply
  • October 2, 2023

Well. There still needs to be an answer or solution to this issue. The problem persists today.


I’ve found a quick solution and it’s worked for me.

Setup before fixing it:

  • I’ve made a component with atomic design principles
  • I publish my component
  • I’ve linked my destination file to my library

My problem:
When copy/paste the main component, certains atoms detached automatically.

Solution:

  • Rename all the components that were detached without putting “_” (Example: order_type ==> orderType)
  • Publish your component
  • Update your destination file

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