Skip to main content
Question

Unsolvable error after importing an existing project made by someone else

  • May 6, 2026
  • 3 replies
  • 32 views

Similiw

Here is the error: TypeError: Failed to fetch dynamically imported module: https://app-aeqw524lvvf2iionbdlcy6i644vdpsps3ywic6xscmfy4bys3o6i.makeproxy-c.figma.site/src/app/App.tsx
 

Figma can't manage to correct it whatever information I give it. The issue seems to be on one of the buttons of the header of the app, but it can't find it. The person who sent me the project has absolutely no problem opening and bring modifications to it. All my Figma Make credits are falling into this error correction, which doesn't lead anywhere. I somehow manage to access it correctly sometimes, but this is a rare case where the version loaded instead is not completely updated, I'm not really sure how it works. Can you help me?

3 replies

adamsmasher
Figmate

Hey ​@Similiw! Thanks for your post - sounds like you’ve done a lot of troubleshooting between yourself and the other person who works on the project with you.

 

Usually you can get Make to resolve the error for you by prompting it to fix it, though from what you described it doesn’t appear to have done that. Are you trying to revert to previous versions? I assume that’s what you mean when you say that you have a version that loads that is not completely updated. This is expected since it’s an earlier version of the app and is a solid way to get around the issue. If you do revert, note the changes that aren’t present so you can prompt Make to re-add those changes. You can even include the error message as part of the prompt and ask Make to make sure to watch for changes that might produce errors like that.

 

Having said that, if you keep seeing this error then I’ll help make a ticket for you so our support team can look into this.


Similiw
  • Author
  • New Member
  • May 8, 2026

Good morning, and thanks for your answer!

I do not revert versions actually. What I do is simply refresh the page of my project; sometimes the error occures directly, and sometimes the project appears perfectly functional and is displayed visually. When it is the second case, the page updates itself automatically after a few moments to display the same error again, but this is enough time for me to see the changes and continue asking editions to Make.

I am not sure it has any link with this problem, but I visualized logs message on the console with F12, and found this:
Access to image at 'https://www.gravatar.com/avatar/7e58ed96369c3e1a2ec85b5c7af5cf72?size=240&default=https%3A%2F%2Fs3-alpha.figma.com%2Fstatic%2Fuser_f_v2.png?c=1' from origin 'https://www.figma.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Understand this error
www.gravatar.com/avatar/7e58ed96369c3e1a2ec85b5c7af5cf72?size=240&default=https%3A%2F%2Fs3-alpha.figma.com%2Fstatic%2Fuser_f_v2.png?c=1:1  Failed to load resource: net::ERR_FAILED

To summarize more clearly the context of this situation: my friend first created this design. He then sent it to me as a .make so that I can import it on my account and continue working on it. But this error appears the way I described it, while he doesn’t ever have any problem the project on his side, even though I sent it back to him after having done some modifications.
Is it possible that even if he sent me the project by exporting a file, the fact that he didn’t add me as collaborator for the project on his side raises this issue?

Thank you in advance for your answer, and have a good day!


adamsmasher
Figmate

That’s super helpful info, ​@Similiw! Thank you for sharing it.

 

Just to clarify what you are seeing again, it does one of two things:

  1. You see the error regarding the app.tsx import right away and are unable to make changes. Or;
  2. You don’t see that error at all, but see the CORS warning and can then make app updates. 

 

Is that correct? The CORS warning isn’t too big of a deal and is related to loading content from another server (seems like Gravatar doesn’t want to serve an avatar image). If you want to learn more about this particular issue, this article on Medium about CORS warnings explains it in a pretty straightforward way. The issue loading the root module could be something like a network issue, ad-blocking software, or a VPN, which also makes sense given your collaborator is never seeing the error. Because it’s intermittent, I’m less inclined to think it’s ad-blocker software, and more likely to be something network-related. 

 

Do you use a VPN, or are you behind a corporate firewall at times? I’m wondering if there’s something with your network or wifi connection that is different when the file loads correctly versus when it doesn’t.