Skip to main content

The component magically changes when transferring from one file to another


Aleksandra Kormashova

I made uikit, published the library, and started using it in another file. Unfortunately, the component has magically changed, which greatly complicates the work

 

2 replies

  • Figmate
  • 2084 replies
  • May 29, 2025

Hi ​@Aleksandra Kormashova,

 

I've had a look at the pictures you shared, and I see the difference in how the nested objects appear in your layers panel.

 

I want to make sure I understand correctly: are those two “Card” instances from the same main component, but they look different in your file(s)?

Could you please double-check if they're from the same main component by using the "Go to main component"? Here’s the detailed instruction: Find main components


If they are from the same main component, please let us know.

In that situation, our support team would likely need to review both the library file and the file(s) where the instances are placed to understand what might be happening.

 

Thanks,


Nándor Danyi

Similar issue here.

I have 1 Figma file set up as a Design System, it contains all the components that are used in about 5-10 other Figma files (let’s call them UI files).

The components from the DS file are published and added to the UI files via the Assets panel.


There is one component that when copied around it either pastes into the UI files correctly, or mostly incorrectly. This component has a nested component inside it (List Item Group). The nested component is modified in this component (Details modal)

List Item Group
Details modal

The nested List item group component at some point changed back to it’s unmodified state within the Details modal component.

This is problematic because it was already used on multiple screens, and now they are not showing what they should.

Also when copying it from the library, in some files it shows up correctly, and some files incorrectly. This randomness can also differ between pages within a Figma file, e.g. in one page it show up OK, on another page not OK.

No matter where it is used, the connection between the component and the library is correct (always points to the right component in the Library)

There are no naming inconsistencies or incorrectly added properties to the component.

When the incorrect component gets pasted in a file, the nested component inside it looks like a previous version of that component. This I can tell by remembering, that the List Item Group was improved by having its own nested components added as a property. The incorrect Details modal loads this old version for some reason.
 

Older version
Newer version

 


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