Definitely still having issues with this as well. And it’s random as well; one day components are working fine, then I open up Figma today and suddenly half my components just stop working despite me not having touched anything in between.

The QA on these updates seriously needs to be increased because Figma has been inconveniencing a LOT of designers lately with these rampant bugs

I’ve reported this issue a week ago, still haven’t heard from Figma. I’ve send the form to the support team and link as @dvaliao said so, and nothing…

Hey @Adriana_DAguiar,

Sorry to hear this! We don’t see any tickets in our system associated with the email address associated with your Forum account. Did you use another email? Do you have a ticket number? Once we locate your ticket, we can try to escalate it to the right team.

Hello, I did fill the form as you said and shared the file with the support team. I’ll do it again if it’s need it

That’s odd. Thank you for letting us know. We can now see your recent ticket #738343, and someone from our Technical Quality team will reply to you soon!

Thanks man, works for me after renaming. Doesn’t work after reseting name back. Still better than nothing, but it is a real pain as thats part of our design system and i should provide some guideance how to use that component 😕

I’m in contact with the support team, thanks 🙂

Problem solved! Thank you support team, impec! 😀

I am facing problem in prototyping, My Component is a nested component and while it should override the interactions that were inside the component, now it’s not doing that and also, It’s automatically resetting the scroll position, even when it’s not checked.

I’ve got the same problem… How can I fix it?

I have a sidebar menu made on a component and there are buttons inside (hovers animation made on external components). Now “On click” function in the prototype has stopped working - the button should lead to the next state of main component and after the update, unfortunately, it leads to an external component … this is weird

I’m still having this issue. I tried renaming every layer differently but the prototype behavior is entirely random. Resets the overrides on occasion, sometimes it decides to work. But it’s not consistent. It’s having a very unexpected and arbitrary behavior. I created a ticket hoping someone shares light on how to solve this exhausting issue.

Same shit. When I use interactive component inside an other interactive component — all props and states crashes at random.

First discovered this in May. It somehow had gone away after a week or so. Now I have to do another UX text and it’s back.

Are people still experiencing these issues?

For me, interactive nested components keep resetting to their default state when prototyping, regardless of the variant selected in the design file.

Just running into this issue suddenly now. components in interactive prototype mode are resetting from screen to screen and not staying in the state I set them to for that screen. Very difficult when trying to walkthrough flows with people in a clear and understandable way. I’ve got multiple of the same component on a frame (with 10+ frames in a flow) and am not keen on having to create a unique name for each component instance in each frame. HAs there been any updates about solving this?

Hey folks, haven’t built a new prototype in a while, and was building one last night when I noticed what I think might be the same or very similar issue to quite a few bugs and issues I’m seeing posted here. Might not solve everyone’s issues but I think some are similar to what I was experiencing so it might help someone.

After some experimenting and opening up some old component libraries with built-in prototype interactions, I noticed a little link at the bottom of their interaction panels telling me I could optional update to new state management:

I think I somehow missed the signifance in this update, or maybe never got a ‘new’ feature prompt about this but there is an article about all the changes here, and IMO they’re quite significant to the point of changing the technique for building many common components dramatically (think things like tab bars composed of individual tab components — instances of those now ‘maintain’ state ACROSS navigated frames)

This solved all my confusion, and doesn’t really matter for older libs as they appear to be version locked to the old state management — but for anything new my old techniques were causing all sorts of bugs where things weren’t keeping their variant settings across navigated frames.

(Side note as annoying as this was at first, it’s now possible to do a heap of really cool stuff like build prototype interactions that set active button or tab states inside the lowest component level and have that state remembered like magic across main prototype navigations)

I suspect this renaming workaround is working because of the changes Figma made to component state management in prototypes. I could be wrong about your specific situation(s) but I think it’s a feature not a bug (however unintuitive — it definitely threw me for an hour or so not succeeding at building prototypes the way I always have).

@MattFannin I really appreciate your post. It helped me uncover what was going on with my prototype.

So there’s definitely a bug here. The problematic component being used in my demo was set to the old style, having been pulled from an older project. Just messing around, trying to get a feel for the functionality I accidentally fixed he issue.

I changed the component into the new style and back to the old one, then published the change. Now it’s working properly although I still don’t quite understand why. The event I changed was a hover, unconnected to the third variant I was trying to use. Maybe it just cleared up whatever issue was present in the component.

Either way, I find this functionality clunky but I’ll have to play with the updates to see what’s on offer.

Wow, this bug is a giant hassle. Just what I need while I’m scrambling to fix my portfolio (as far as I know you still can’t easily make copies of a design system with it’s linked files without spinning the plugin roulette wheel). Figma! You make a great product, but you need to not ship things until you have test things thoroughly. I THINK that the changing to the new interaction style then changing back to the old style is working for me. But it’s going to take a very long time to fix all that I need to fix. WHAT A FRUSTRATING SITUATION.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.