Skip to main content
Paul_Lyons
Paul_Lyons
New Participant
March 16, 2021
Question

Prototype bug - My prototypes flick between random screens when Interactive components are turned on

  • March 16, 2021
  • 30 replies
  • 9914 views

I have quite a big file with many components in use for table cells, buttons, form elements etc, and have been using Interactive components for link / button hover states, check boxes etc.

My prototypes were working well until the last update. Now during random parts of the flow, my prototype randomly jumps between a series of screens, making the prototype unusable.

I went though all pages & elements, checking I didn’t have any stray ‘hover’ or ‘after delay’ actions in place and they were not any. I did however notice that some flows were fixed, by changing some duplicate frame names I had. The issue would however, pop up elsewhere in the flow and could not be fixed by adding unique frame names.

The only thing that stopped the bug, was when I turned off ‘Interactive components’ for the prototype. The prototype then worked fine after that (minus my micro interactions).

Bit of a strange bug, but thought i’d share for investigation.

    This topic has been closed for replies.

    30 replies

    Show previous replies
    Jesse_Wang
    Jesse_Wang
    March 25, 2022

    Hey andrew - Is the fix rolled out to the desktop app or figma mirror? Both say I’m on the latest but I’m still experiencing the slide skipping issue on iPad. Thanks!

    smn
    smn
    October 21, 2022

    Hi there, I am experiencing a similar thing. I have a prototype with a slide-in menu. The menu items link to individual pages within the prototype. If I select one of the menu items I would expect the prototype to keep playing from the set page instead it jumps back to where it started. This results in a total mess as the flow of the story is totally butchered…

    Is there anything that can be done? Never had this before.

    SohrabNiroo
    SohrabNiroo
    New Participant
    October 28, 2022

    The problem have been fixed when the component properties introduced

    Just make a varient button component with 3 states ( Main, Hover, and active )and give it properties, then make a sidebar and use that component to have items and change its properties and make it another component.

    Now to put the component inside the needed frames and give each frame which item should be active.

    Now go back to the sidebar and prototype by navigating each item into the right frame

    it should work perfectly.

      bradk
      October 28, 2022

      FYI - This doesn’t seem to happen on the desktop app. Only on the browser!

      smn
      smn
      October 30, 2022

      Thanks Sohrab, I’ll give it a try.

        Tamar_Ziri
        Tamar_Ziri
        June 21, 2023

        ❣️ I FOUND A SOLUTION ❣️ (at least it worked for me, hopefully it helps you too!)
        Go to your chrome settings> system> disable ‘Use hardware acceleration when available’> relaunch> settings> system> enable ‘Use hardware acceleration when available’> relaunch.

        Tameem
        September 27, 2023

        SOLUTION:

        First of all I tried the above “solution” but that didn’t work. My suggestion is to do the following:

        1- Ensure that your prototype variants swap “When the video ends” rather than “After Delay” with a delay set for the duration of the video.
        2- Select the “Reset Component State” option
        3- Untick Autoplay

        Still flickers…but SUPER fast and not noticeable.

        Dimitar_Tsonov
        Dimitar_Tsonov
        August 20, 2024

        And almost an year ahead, this issue is here again after the update with the new UI!
        Figma team, please fix this. It makes the prototype unusable… the only way I found so my prototype works so-so is to refresh it like several times without changing anything. When start changing/adding screens/elements/components, the issue comes back again, until I reload the tab and refresh after that several more times… It’s absolutely annoying and frustrating.

        Saad_Khan
        August 22, 2024

        Just encountered this bug and i cant use the prototype feature at all. I have a demo due in 2 days and i dont know what to do. @Andrew_Chan please help.

        CJSurita
        CJSurita
        August 29, 2024

        what worked for me was changing my component animation to instant instead of smart animate.

        Terms & ConditionsAccessibility statement