Skip to main content
Arno140
Arno140
New Member
January 27, 2026

Figma Make - Unable to publish prototype update - "Something went wrong" error

  • January 27, 2026
  • 64 replies
  • 1384 views

Hello, I'm reporting a persistent bug in Figma.

Issue: Unable to publish prototype updates via the Preview tab. Error Message: 'Something went wrong, reload and try again' (in red). Start Time: Jan 27, 2026

Troubleshooting steps I've already taken:

  • Refreshed the page;

  • Switched browsers and used Incognito mode;

  • Restarted both the app and the computer;

  • Duplicated the file and attempted to publish (the error happens in the new file as well).

Please let me know if you need any logs.

    This topic has been closed for replies.
    Pinned Reply By Junko3

    Hi there,

     

    Thanks for reporting the publishing error you’re seeing.

    A fix has been implemented for issues affecting the publishing of Figma Makes or Sites with code components. You can find more details and the timeline here: https://status.figma.com/

    Please fully refresh Figma and check if things are back to normal.


    Thanks again for your patience while we sorted this out.

    64 replies

    Show previous replies
    Julius von Ingelheim
    Julius von Ingelheim
    New Participant
    February 18, 2026

    Hey everyone. Had this publishing issue occur for the first time for me now. I tried all the fixes that were discussed here but none of them work sadly. I also tried to duplicte the file, let colleagues try to publish it etc and nothing seems to fix this issue. Any other ideas on what I can do to be able to publish this file? 

    All other files I can publish without a problem btw.

     

    BR,

    Julius

    Celine_
    Figmate
    Celine_
    Community Support
    February 18, 2026

    Hey ​@Julius von Ingelheim , thank you for trying the steps mentioned in this thread. I can see you’ve already reached out to our Support team. I can confirm that your case has been assigned, and I’ve added a follow-up note internally for visibility. For reference, your support ticket is #1752060.

    As a heads up, we’re currently experiencing a higher ticket volume, so replies may take a bit longer than usual. Someone will be in touch as soon as possible. We appreciate your patience!

    Julius von Ingelheim
    Julius von Ingelheim
    New Participant
    February 18, 2026

    Hey ​@Julius von Ingelheim , thank you for trying the steps mentioned in this thread. I can see you’ve already reached out to our Support team. I can confirm that your case has been assigned, and I’ve added a follow-up note internally for visibility. For reference, your support ticket is #1752060.

    As a heads up, we’re currently experiencing a higher ticket volume, so replies may take a bit longer than usual. Someone will be in touch as soon as possible. We appreciate your patience!

     

    Thanks Celine. I finally found a solution with some deep digging in the file and this was the issue + solution (if anyone might try something similar as a fix):

     

    Root Cause In vite.config.ts, resolve.dedupe includes three Lit sub-packages: '@lit/reactive-element', 'lit-html', 'lit-element' dedupe forces Rollup to resolve these from the project root of node_modules/. But with pnpm's strict layout, those three packages are never symlinked at the root — they only exist inside the .pnpm virtual store (at .pnpm/lit@3.3.2/node_modules/). During vite build, Rollup can't find them at the root and silently fails with no error output. The Fix Edit vite.config.ts — remove @lit/reactive-element, lit-html, and lit-element from the resolve.dedupe array

      Celine_
      Figmate
      Celine_
      Community Support
      February 18, 2026

      Glad to hear you were able to find a fix. Thanks for following up and sharing your solution with the community!

      Terms & ConditionsAccessibility statement