Prototype issue with nested components

Hi! I have created a Sign In card with several nested components (the button, the input field, the checkbox), however when i interact with it in presentation mode it breaks (random parts of the design disappear), as seen on the first gif. I have detached the button which seemed to resolve most of the issue, however the checkbox still breaks. This issue persists since weeks, I can’t use any nested components if I want to have a working prototype, however this means I can’t reuse anything, my project is full of duplicates. Did this happen to anybody else? Does anybody know how I can resolve this? Thanks in advance.
Component
figmagif
figmagif2

Hey @Lyonixa, thanks for reaching out and sorry to hear you’re having trouble with this!

From what you’ve described and the screenshot and screen recordings that you’ve shared, it’s hard to be sure what may be causing the issue. Are you able to share a link with us, so we can take a closer look at how your layers have been set up?

If so, please include a link to the file, and share edit access with support-share@figma.com, so we here in the community can take a closer look.

Hi @dvaliao , thank you for replying!

In the meantime, while reading through the forum about Figma being slow (which I also experienced in the past couple of days), and how some people resolved it by detaching typography variables, I also deleted mines (for font family, weight and size) and so far it seems like it worked (everything got back to normal - prototypes included), however I have no clue how this is related. I did start to have both unexplainable prototyping problems and Figma getting very slow (both in desktop app and browser) since i started to switch from styles to variables.

Could this be a bug caused by variables indeed?

Hey @Lyonixa, thanks for following up!

Yes, we were experiencing a bug with typography variables late last week through the weekend.

The team slowly rolled out a fix yesterday though. Please refresh your file and let us know if you run into any further issues.

Keep in mind that there still may be some slowness as the file loads and tries to layout all the nodes in the file, but it should eventually settle.