Prototype interactions disappear after a library update

Hey ​@David_Chung 👋 Welcome to the community! Can you share a bit more about your setup? Also a full screen recording of the issue happening from start to finish is always super helpful for our community members. Happy to dig in and having a few more details will help me find specific resources for you. — Jaycee

+1

I’m having the same issue. On my design system file, the master has interactive prototype (e.g.: Hover state). When publish this to the library to use in other design files, this interaction disappears.

Thanks for the +1, ​@Luongnd, and for the detail from you both so far.

• ​@David_Chung, we've got your ticket. We're tracking your report under case 2085476, and I've passed this thread to the team handling it so they have the full context. File access will move things along fastest, since it lets us compare a component that always loses its interactions against one that never does. Replies will come to the email you filed with. 📥
• ​@Luongnd, could you post a screenshot of the Prototype tab with the main component selected, showing the hover interaction as it's set up? How that interaction is built changes what's likely going on, and seeing it will tell us whether you're hitting the same thing as ​@David_Chung. 🔍

If you'd rather not post it publicly, you can send it through the Support Hub instead: Type in “report a bug” → include the file URL → give support-share@figma.com view access. Whichever's easier for you!

I can confirm the bug, with interaction disappearing. It is not only frustrating, but has a huge impact on my work. The prototypes are clients facing majority of time and there is no trust that the prototype would be working next time when it run. I read about the similar Figma’s prototyping tool bugs 3-5 years ago. It seems like no one cares and I just cannot rely on the tool and re-fix again and again the same interactions links. Looking for a just reliable prototyping tool, without AI crap.

Hi all, following up with an update. Sorry to hear you’ve encountered trouble with this as well, ​@Vitalii Nikiforov.

A similar issue was reported in this thread: Default variant interaction changes when a published component from a library is used in a new file. There, a variant interaction worked in the library file, but on instances placed in other files, it lost its link. We escalated that report to our engineering team. They investigated it using the files that were shared with us, and a fix recently went out.

To help us see where each of you stands, could you let me know:

1. Does that match what you're seeing? Please have a look at the other thread and let me know whether it sounds like the same problem or something different.
2. Is it still happening? Let me know if it happens again after your next library update.

If it's still happening, file access will let us confirm whether it's the same issue or something that needs a closer look:

• ​@David_Chung, reply to the email for case: 2085476, with the file URLs, and give support-share@figma.com view access.
• ​@Luongnd and ​@Vitalii Nikiforov, please submit a request via the Support Hub → Report a bug. Include the file URLs and a link to this thread. Vitalii, your post came after the fix went out, so your files would be especially helpful.

And if it's working for you now, a quick reply saying so helps just as much. 🙏🏻