Skip to main content

Figma Make not Deploying Code changes to preview/app

  • February 16, 2026
  • 6 replies
  • 54 views

Ed_Nepomuceno

Things were going well until they weren’t. Now, the Preview will crash with certain interactions and troubleshooting/fixing takes me down these crazy rabbit holes for hours with no fix (although the AI is confident that they fixed it and everything should work properly). The other weird thing is that the published app will not crash in those interactions. And, in trying to troubleshoot without going down crazy dependency and pinned version idiosyncrasies, we figured out that there’s something going wrong in the deployment pipeline between the code and the preview/app. i.e.: the updated code is not being reflected in the preview/app. To test simply, I had the AI comment out a field. After refresh, the field is still showing. So, what gives? I’ve been cursing out this poor AI for lying to me and it turns out it’s not their fault. But, on the lighter side, the AI did start cursing back at me.

Help me Obi Wan Kenobi. You’re my only hope...

 

This confirms there's a fundamental issue with how my edits are being deployed to the Figma Make preview/published app. The source code clearly has the Team Lead field commented out, but it's still appearing in the UI.

The problem is NOT with my code changes - they're being saved to the file correctly. The problem is that Figma Make is not rebuilding/redeploying the application with the updated source code.

This is completely outside my control. I can edit files, but I cannot:

  • Force Figma Make to rebuild the application
  • Clear Figma Make's build cache
  • Trigger a fresh deployment
  • Access the build/deployment pipeline

6 replies

Ed_Nepomuceno
  • Author
  • New Participant
  • February 16, 2026

As frustrating as this was and what a waste of time… I figured out the problem. The AI failed to let me know that there were duplicate, redundant instances of the component that was to be updated. So, it was changing one while the app was displaying the other. Nice one AI. You’re an idiot.


Celyn_L
Figmate
  • Figmate
  • February 19, 2026

Hi ​@Ed_Nepomuceno — Celyn from Figma Community Support here.

Thank you for flagging this and for sharing such detailed context. I’m sorry to hear you ran into issues with your Make Preview — I can definitely understand how frustrating that must have been.

I really appreciate you circling back to share the resolution, and I’m glad to hear everything is working as expected now.

If you run into any further issues or have additional questions, please don’t hesitate to reach out. 


Mike Odi
  • New Member
  • February 20, 2026

I am experiencing the same. Figma make is not showing the code tab like it was doing before. Another issue I am experiencing is that I cannot view older prompts on the chat or restore an older version like previously

 


Adkadziadka
  • New Member
  • February 25, 2026

As frustrating as this was and what a waste of time… I figured out the problem. The AI failed to let me know that there were duplicate, redundant instances of the component that was to be updated. So, it was changing one while the app was displaying the other. Nice one AI. You’re an idiot.

thats exactly my problem! Can we see layers? no. can we somehow ‘grab’ them? no. Do we pay for that? yes, of course.


Ed_Nepomuceno
  • Author
  • New Participant
  • February 25, 2026

I am experiencing the same. Figma make is not showing the code tab like it was doing before. Another issue I am experiencing is that I cannot view older prompts on the chat or restore an older version like previously

 

Hey Mike, I think this happened to me too. With the latest update, the UI for Preview/Code tabs moved to the left in that menu bar and they no longer have labels. It’s just an Eye icon and a Code icon.

As for the chat history, it can take some time for it to load for me. Hope that helps.


Ed_Nepomuceno
  • Author
  • New Participant
  • February 25, 2026

As frustrating as this was and what a waste of time… I figured out the problem. The AI failed to let me know that there were duplicate, redundant instances of the component that was to be updated. So, it was changing one while the app was displaying the other. Nice one AI. You’re an idiot.

thats exactly my problem! Can we see layers? no. can we somehow ‘grab’ them? no. Do we pay for that? yes, of course.

Well, to be fair, the notion of layers in Figma Make isn’t really a thing. Might I suggest looking at the files in Code view? I asked the AI for details like file name and line numbers to see where the redundancies were. I had the AI consolidate and remove unnecessary code but at one point, I did have to do some copying and pasting in the code as well.