Figma Make Broken after latest update

Hey ​@sandeeptz — welcome to Figma Forum, and thanks for bringing this to our attention. Sorry to hear about the issues with your Make prototypes.

I wanted to check in, are you still seeing these errors and rendering anomalies? If so, the following details would help me dig into this:

1. Platform and version: Is this happening in the browser, the Figma Desktop App, or both? If you're on the Desktop App, could you confirm you're running version 126.1.2 or later?
2. Error messages: What specifically do the error messages say? Please check whether any of them match the known issues listed here: Troubleshoot in Figma Make → Error messages.
3. Screenshots or video: You mentioned the errors seem to reference underlying code — if you're able to capture what you're seeing (screenshots or a brief recording), that would help ensure we're looking at the same thing.
4. Steps to reproduce: Could you walk me through what leads up to the errors, including which elements have lost interactivity? That'll help me test on my end.

If none of the above points to a fix, I can open a case with our Technical Quality team so you can work through this with them directly. I'll keep an eye out for your reply. 🙏🏻

1. Mac, Figma Desktop App version 126.1.2
2. ⚠️ Warning: Encountered two children with the same key, `%s`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version.%s null
3. What make tells me the issue is: 

   1. Understanding the _fgT, _fgS, _fgB Props Error

      These props are Figma Make inspector tracking attributes that get automatically added to components during development to enable the visual inspector and hot-reloading features. They're environmental artifacts, not bugs in your code.

      What's Happening

      React DOM is warning you because these non-standard props (like _fgT, _fgS, _fgB) are being passed down to native DOM elements (like <div>, <button>, <input>, etc.), which don't recognize them. React expects only standard HTML attributes on DOM elements.

      Why It's Happening

      This typically occurs when you're spreading props directly onto DOM elements without filtering:

      // This causes the warnings:
      function MyComponent(props) {
        return <div {...props}>Content</div>;
      }
      

      The Figma Make tracking props get included in props and then spread onto the <div>, causing React to complain.

      ​​​​​​​
4. No steps, it is on initial load of my Make files, it loads, refreshes, and then shows multiple errors to then “fix for me” but I’ve had to revert as this action breaks more than it fixes.