Have also restarted Figma and my Macbook multiple times to no avail. Is happening in both desktop app and browser versions. And seems to affect previously made prototypes too. Interactive components within them are not functioning.
I’m facing the same issue here. I was trying to create a new component and nothing was working, then I’ve checked old files and were not working also.
Desktop and browser has same problem
I’m having the same issue
Same issue. Prototypes were working perfectly Friday. They do not this morning.
Scratching my head for 2 hours… Got back in version history to last week version.
Wasted my morning progress, but at least I know now it is not my prototype.
I can now move forward. Thank you for sharing
Same problem here. Nest interactive components not working.
So, I used to create components for menu with “change to” so I could make the text bold while on hover and it used to work just fine, but now it just won’t change during prototype and I don’t understand why…
I can still change manually on the file, but when I press play, nothing happens while on hover, is that a bug?
I’m having the same issue. “Change to” interaction simply doesn’t work in my prototype.
All prototyping created in the library doesn’t work anymore. The checkbox for interactive components is not present anymore also. Only prototyping between frames on projects still works.
Same issue. @Figma_Support My entire company can’t a prototype right in the middle of the sprint. @Figma_Support
✋ Also experiencing this today.
this is a bug across all of Figma currently. interactive components is not functioning at the moment
Experiencing the same issue across the board.
I’m also experiencing this issue. New and old interactive components are not working as intended
OMG, I thought I was the only one. I spent the last hour reverting the file to previous states with no impact. 🤪
i cant find
Enable interactive components
Hey All, this is a bug that our team is proactively working on. We’ll keep you in the loop as we work on a fix.
Same issue here. I’ve spent several hours of valuable time trying to fix it.
Same here, stopped working about 1 hours ago
Why is this marked as solved? Still not working for me.
Hey All, this is a known bug that our team is proactively working on. We’ll let you know once a fix has been pushed.