Skip to main content
Question

Bug report: React generation error (motion/react) is blocking updates

  • March 25, 2026
  • 1 reply
  • 16 views
Lecrons

Hi Figma Team,

I am writing to report a critical issue with the code generation feature for React. There is a persistent compatibility/import error being generated in the code (specifically failing to resolve "motion/react" in Vite).

Because of this specific React connection issue, the AI attempted to resolve the error multiple times in a loop. As a result, it consumed all of my available AI credits, and the error still persists.

To keep my website running, I had to completely revert to a previous version. However, this means I am now entirely blocked. If I try to make any new changes or updates to the page, the system triggers the exact same React error, fails to compile, and unfairly consumes more credits without applying the updates.

Summary of the impact:

  • Bug: Generated code fails with Vite internal server errors regarding motion/react.

  • Consequence: AI attempts to fix it drained 100% of my credits without success.

  • Current state: Blocked. I cannot update my design without losing more credits to the same error.

Could you please investigate this code generation bug? Additionally, I would appreciate it if you could refund/restore the credits that were lost due to this automated system failure so I can continue my work once it's fixed.

Thank you for your time and help,

1 reply

Celyn_L
Figmate
  • Celyn_L
  • Figmate
  • March 27, 2026

Hi ​@Lecrons, Celyn from Figma Community Support here.

Thanks for taking the time to share such a detailed report — that context is really helpful.

I understand you’re encountering a recurring React/Vite error (motion/react not resolving), and that the issue is still persisting despite multiple attempts to resolve it.

I’ve gone ahead and created a support ticket (#1817202) on your behalf so the team can take a closer look at both the code generation behavior and the credit usage tied to this.

To help us investigate this properly, could you share a bit more detail when you have a moment:

  • The Figma file URL where this is happening
  • A screenshot of the error, if available 

You can reply to the support email with these details. When you’re able to, please also share your impacted file with support-share@figma.com and grant “Can View” access — this will not impact your billing and will allow us to reproduce the issue and investigate with Engineering.

On the credits side, I’ve included your note in the ticket so the team can review what happened there as well.

Appreciate your patience while we dig into this — we’ll follow up with you via email as soon as we have more updates.

Terms & ConditionsCookie settingsAccessibility statement