Skip to main content
Question

CRITICAL: All "Figma Make" files crashing immediately - React Router Error

  • January 22, 2026
  • 12 replies
  • 224 views

Maricruz

Hi Figma Team,

I am experiencing a critical issue where all my Figma Make files have suddenly stopped working. The preview crashes immediately upon loading with a white screen or error message.

This seems to be a deployment regression on your end, as it affects multiple files that were working perfectly before.

The Error: The console throws a React Router v6 error stemming from makeproxy-c.figma.site. It seems an undefined component is being passed to your router configuration.

Stack Trace:

Error: [undefined] is not a <Route> component. All component children of <Routes> must be a <Route> or <React.Fragment>
at invariant (react-router-dom.js)
at createRoutesFromChildren (react-router-dom.js)
at Routes (react-router-dom.js)
...
Source: https://app-7rewowbl35pf7ves4z6mxxdyr7d3zoduh36vgxqfkug7i6yt7ncq.makeproxy-c.figma.site

Steps Taken:

  1. Cleared Desktop App cache.

  2. Tried accessing via Chrome/Edge (same error).

  3. Duplicated the file (same error on the new copy).

Please investigate this urgently as it is blocking all work related to Figma Make.

Thanks.

12 replies

MS Creative
  • New Member
  • January 22, 2026

Hello, 

I’ve been working on a website prototype in Figma Make. This morning, when I opened the Figma app to continue working, I was greeted with an “A Little Help” message and a button labeled “Fix for me.” I’ve seen this before and it usually resolves the issue, but not this time.

When I click “Fix for me,” the file reloads, but the preview still doesn’t display. I’m immediately met with the same prompt again. On one occasion, after clicking “Fix for me” more than 10 times, a version finally loaded, but it was clearly not my work. It was a severely diluted, butchered version that represented maybe 1% of the actual project.

 

^ The preview thumbnails are also empty now.

 

I’ve tried every solution I can think of, including:

  • Resetting Figma

  • Restarting my Mac

  • Manually refreshing

  • Restoring older versions

  • Clearing the Figma cache

…and plenty more, all with no success. I’ve spent over 25 hours building this project and another 3 to 4 hours trying to recover it. If the work is truly lost, that’s a massive travesty and an enormous waste of time. I’m a huge advocate of Figma, but this issue has been a real headache.

What makes this even more baffling is that a colleague at the same company, using their own Figma account, can still see the preview without any issues. That part genuinely boggles the mind.


  • Figmate
  • January 23, 2026

Hi ​@Maricruz

 

Thanks so much for flagging this! I’ve gone ahead and shared your report with our Engineering team internally.

This may be related to an issue our Engineering team is currently working on.

I’ll share an update as soon as we have more information.

 

Thanks!


MS Creative
  • New Member
  • January 23, 2026

Hello, 

Still awaiting a response. Make is suggesting that it’s a severe bug and to ‘Contact Figma Make Support‘.

I have also received this message ‘I cannot fix this from the code side because even the simplest possible React code fails. This requires Figma Make platform intervention. Your full website with all pages, navigation, footer, and beautiful design exists and is correct - it just can't load due to this caching issue.’ – I have already cleared the cache.

Thanks,

 


Celyn_L
Figmate
  • Figmate
  • January 23, 2026

Hi ​@MS Creative — Celyn from Figma Community Support here. 

Thanks for flagging this and for sharing the detailed context. I’m sorry you’re running into issues with your website prototype in Figma Make.

I’ve created a support ticket #1704264 on your behalf, our support team will work with you to have this resolved.

Appreciate your patience 🙏


Shane Waters
  • New Participant
  • January 23, 2026

I just updated my Figma Desktop App and it seems after every 3rd request in Make it will crash.  I had this happen in previous version 1 or 2 times a week, but not every 3rd or 4th request. 

 


Adam Canfield

hI ​@Celyn_L - we are also experiencing this problem. I have seen mutiple items on this forum too raisign it. I think it’s a Figma wide issue.


Adam Canfield

It’s now showing “Route” issues and switch React Router back and forth. Sometimes it loads for a few seconds


Celine_
Figmate
  • Community Support
  • January 23, 2026

Hey ​@Adam Canfield , thanks for flagging this! I’ve gone ahead and merged your comment into this thread.

This appears to be a separate issue, and to help our support team investigate further, please submit a bug report via the Support Hub, and include a copy of your file so they can take a closer look at it.

To do that: Go to the Support Hub / Click Start a chat / Type “Report a bug” / Include a direct URL of the affected file

Please also share edit access to the file with support-share@figma.com (our official Support account) so the team can take a closer look. You won’t be billed for this access.

Once you’ve submitted the report, feel free to let me know, I will escalate it internally. Thanks for your patience!


Adam Canfield

Hey ​@Celine_  ​@Celyn_L - 
Is there any status update available for this? It is still happening for us. The Figma Service site doesn’t mention any active Make issues.

https://status.figma.com/


djv
Figmate
  • Community Support
  • January 23, 2026

Hi All, thanks for your patience while I team worked towards a fix! 

We just pushed an update that should resolve these issues. Please refresh your Make files and please let us know if you run into any further issues.


MS Creative
  • New Member
  • January 26, 2026

Hello ​@djv 

There’s no difference for me ☹️

Thanks,


Celine_
Figmate
  • Community Support
  • January 26, 2026

Hey ​@MS Creative , thanks for letting us know! I can see that you’re already in touch with our Technical Quality team, and they’re currently waiting for your response so they can continue investigating.

For reference, your case number is #1704264. Please continue the conversation via the secure support form so the team can take a closer look at your case. Thanks!

Sharing an update here for visibility: it is working now for MS Creative.