Hey @Vojtech Petrasek , thanks for the detailed report and screenshot! I tried reproducing this on my end, but I wasn't able to trigger the same behavior. Since this sounds like it could be specific to how renamed nested instances are resolved in Dev Mode, I'd love for our team to take a closer look if the issue is still happening
A couple of quick questions in the meantime:
- Is this happening across multiple components/libraries, or only with a specific component?
- If you rename the nested instance back to its original name, does it appear correctly again in Dev Mode?
If the issue persists, please submit a bug report to our Technical Quality team via the Support Hub → Click Start a chat → Type "Report a bug" → Press Enter and follow the prompts.
When submitting, please include:
- A link to the affected component/library and View access granted to support-share@figma.com
- A screen recording of the issue
- Steps to reproduce
This will help the team investigate directly. Thanks for your patience! 🙏
Update: I see in the backend that everything is working as expected now! If the issue comes up again, feel free to reply directly to your support case. I’ll go ahead and close the topic here!