Skip to main content

When using “Present” mode the interactions aren’t displaying correctly

  • July 7, 2026
  • 2 replies
  • 5 views

lwilkins5000

Similar issue: When using “Present” mode the interactions aren’t displaying correctly. A simple list of expanding/collapsing containers fails to open any of the containers except 1, despite tapping on other containers. This isn’t happening in Mirror or in “Preview” mode.

2 replies

Jaycee Lewis
Figmate

Hi ​@lwilkins5000 I moved this to its own post so we can troubleshoot together. 

A couple things that’ll give us more info on what's happening:

  • Could you share a quick screen recording of Present mode where you tap through a few of the containers in sequence (including ones that don't open)? That'll show which taps are and aren't registering
  • Are all the containers separate instances of the same interactive component, or one instance duplicated. If so, are they sharing a single variable/state, or does each have its own?

That should help with whether this is a Present-mode bug or something in how the containers are wired up.

Thanks! — Jaycee


lwilkins5000
  • Author
  • New Member
  • July 7, 2026

Hi ​@lwilkins5000 I moved this to its own post so we can troubleshoot together. 

A couple things that’ll give us more info on what's happening:

  • Could you share a quick screen recording of Present mode where you tap through a few of the containers in sequence (including ones that don't open)? That'll show which taps are and aren't registering
  • Are all the containers separate instances of the same interactive component, or one instance duplicated. If so, are they sharing a single variable/state, or does each have its own?

That should help with whether this is a Present-mode bug or something in how the containers are wired up.

Thanks! — Jaycee


This was one component animating across variations. 
I was able to fix it by deleting all Flow Starting points in the file and re-adding them.
I tried it again with a different proto (in the same file) that didn’t have a flow starting point assigned, and it also started behaving strangely, so I guess I’ll make sure every single sample has a flow starting point? This has only recently been an issue, I don’t normally use a separate starting point for the small tests that I run.Â