Skip to main content

In my prototype I have a home screen with two buttons, each with tap interaction navigating to a new screen.

The first time I run the prototype both interactions work fine. But if I go back to the home screen, now only one of the interactions work. It doesn’t matter if I use button #1 or button #2, every time I go back to the home screen button #2 will no longer have an interaction. Button #1 works every time.

I’ve even created a new button (just using a rectangular shape + tap interaction) and the same thing happens with that as with button #2. It works the first time I run the prototype, but if I go back, neither button #2 nor #3 will work while button #1 works just fine.


Is this a bug? Have I done something weird? Am I going mad?

Screenshot 2022-11-11 at 10.14.50


Adding a screenshot to help explain the issue

I have the same issue. Have you solved it?

Sorry since it was 10 month ago I can’t really remember … but just thinking about it now maybe it is possible to solve using the “Reset component state” checkbox.


Screenshot 2023-08-31 at 15.03.27

Hello, guys.


I have the same issue, and it drives me crazy. I have done EVERYTHING:



  • reset interactions

  • deleted all the “extra” frames testing the problematic part of the flow

  • copied frames and made new connections

  • renamed frames with 100% unique names


Nothing helps.


If someone finds the way to solve this problem, I beg tag me.

I’m having a similar issue both as described in the original post, but also my overlay interactions work only sometimes. The ‘background’ overlay appears, but not the actual modal… that only appears sometimes when it feels like 😅

Hi, Karen. I am ashamed to admit, I solved my problem one hour after posting my question here. I was desperate and angry 🙂


In my case, it was a simple human error. There is no Figma’s fault, nor is black magic in it.

Seems that I accidentally copied and pasted frames with connections over existing ones at a certain point while working on a prototype. So as I overlooked that moment, I kept working on the prototype, creating new connections on the top-level frames.


When I started to test the flow, Figma was as confused as I was. The first time it was following the top layer flow (with no problems), but the second time it was going underneath, running through the flow I had for my “old” prototype. When it reached an “old” component with no connection, it seemed stuck to me.

I’ve deleted my “old” prototype that was resting beneath the new one, and everything is working perfectly!


So, if your tap interaction works perfectly for the first time, but has no response on the second, check if you have any “rests”, copies, or duplicates under the prototype you are testing.


Good luck!

Reply


Terms & ConditionsCookie settings