Skip to main content
Question

Component properties resetting and internal icons changing upon publish/update

  • July 30, 2026
  • 0 replies
  • 5 views

Ewon

I’m writing to ask for some advice as I’ve recently run into a couple of frustrating issues while managing our Design System (D.S.). Every time I publish and update, things keep resetting, which makes me honestly afraid to touch any other components. 🥹

Here is a summary of the two issues I'm experiencing:

 

1. GNB Component Properties Resetting to Default

  • Context: About 3–4 months ago, I created a GNB component in our D.S. Figma file, pulled instances into our actual working design files, and set different properties (e.g., Menu A Selected, Menu B Selected) for each screen.

  • Issue: Last week, I made some updates to the GNB in the D.S., published the changes, and updated them in the working files. Surprisingly, all the custom properties I had carefully set per screen reverted back to the D.S. Default! In the past, screen-specific property settings were preserved, but this time everything changed, forcing me to manually reconfigure the properties for every single screen.

2. Token Component Inside Component 'A' Changing When Pasted into H/O Files

  • Context: In our D.S. file, we have 'token + number' components that are used both standalone and nested inside another component ('A'). Yesterday, I updated component 'A', published it, and updated it in the working design file.

  • Issue: Afterward, when I copied and pasted those screens into our H/O (hand-off) file for developers (which has the exact same layout as the working file), the token icon inside the component changed to the D.S. default! At the time of pasting, the H/O file had the D.S. library connected, but not the library of the working file where component A lived. Regardless of library connections, the core issue is that component A's original values were altered rather than maintaining their state upon being pasted.

 

Because values keep changing unexpectedly every time we publish and update, it's making us hesitant to update other components.

Could anyone explain why this keeps happening and if there’s a way to fix it? Also, is this a known bug or issue? Any insights or advice would be greatly appreciated.

Thank you!