Hi,
Since the latest major update, we’ve been seeing a visual glitch with component instances in our Organization.
Almost all instances initially render with the default state of the component (or nested instances), instead of showing the overridden values. The visual state only corrects itself after we interact with the instance — for example:
-
Clicking into overridden text layers
-
Toggling a variant/prop off and on again
📺 YOUTUBE VIDEO OF THE ISSUE IN ACTION: https://youtu.be/GOBF6B7vaO8
---
This is particularly problematic with our icon components, which use a scale vector. We have to swap between styles (e.g. filled/outline variant) on the inner vector before it displays at the correct size.
In the attached video, you can see that our documentation header component first appears in its default state, and only then displays the correct overrides after double-clicking on the text elements.
---
This issue is happening organization-wide, across all files. It’s especially confusing for developers in Dev Mode, since they can’t interact with components to “refresh” them and are therefore seeing an inaccurate visual state of the component.
OS: MacOS Sequoia 15.5/Windows 11 (irrelevant, happening on both)
App: Happening on both Web and Desktop (version 125.9.10)
