Skip to main content
Question

Figma Make: React Warning: “React does not recognize the %s prop on a DOM element”

  • March 11, 2026
  • 4 replies
  • 44 views

m1n3g

 

 

Both of my projects started showing this warning today while using Figma Make. The warning appears in the console and points to a React issue. Is anyone else experiencing the same issue?
 

Any insights or solutions would be appreciated.

 
 
 

4 replies

Eugene87
  • New Member
  • March 11, 2026

I experince similar issues. No solutions so far.


Boris Octalysis

Same. ​@Andrew_Chan ​@seni ​@Gayani_S ​@Tom Reem 

 

My Figma Make freezes on certain elements. I found that it starts to freeze on Dropdown Items, which makes it impossible to work on the interface.

The styles have also changed (some elements have changed color, outlines have been added or removed, which I did not do).

 

There were also errors like this:

But the funny thing is that when you deploy a project to Publish or Static Files, everything is fine. But when you work through the Figma Make builder, errors occur.

I assume this is a bug on Figma's side.


m1n3g
  • Author
  • New Participant
  • March 12, 2026

Same. ​@Andrew_Chan ​@seni ​@Gayani_S ​@Tom Reem 

 

My Figma Make freezes on certain elements. I found that it starts to freeze on Dropdown Items, which makes it impossible to work on the interface.

The styles have also changed (some elements have changed color, outlines have been added or removed, which I did not do).

 

There were also errors like this:

But the funny thing is that when you deploy a project to Publish or Static Files, everything is fine. But when you work through the Figma Make builder, errors occur.

I assume this is a bug on Figma's side.

 



I also suspect this is a bug on the Figma Make side.

 
 
 

YuriiV
  • New Member
  • March 12, 2026

I am experiencing the same issue just today. Seems like it’s something to do with the update. Although, everything works perfectly fine for other Figma Make projects – the issue occurs only with the one.

Team Figma, please fix :)