WeWeb/Figma Import Bug - Weweb says its imported with success, but nothing is imported into weweb

bug #FIGMA Hi everybody, anybody else having problems with the Import from figma on the weweb side? I LOVE THIS FEATURE! But its been broken.

It worked fine a few days ago, but now, when I use the stated proces (builder.io plugin, classic, export code, paste to clipboard, in weweb import from figma) Weweb goes through the import steps and has a small succes pop up in the left corner, but no root section is imported, nothing is imported into weweb, but weweb gives a succes confirmation on the import. I tried to copy big sections, and even just a small text field, but nothing works, so it seems that the problem is on the weweb side?

Regards, Anders

Hi Anders :waving_hand:

What happens if you start a new project in WeWeb and try again?

Did you follow best practices outlined here? Import Figma designs | Documentation

things like: Auto layout, renaming layers

Let me know.


Hi Agustin,
I just tested with just a text field only, and with an image only, so its not something with renaming layers (I used the figma import for the last few weeks without renaming layers I was gonna change anyway and it works fine without renaming.
I just tested in a different project, same problem, I get the confirmation in weweb that import was succesfull, but no section or content is imported in weweb.
(I use the builder.io, classic export, precise, auto layer

Could you please look into it, perhaps you did an update of something?

Best regards, Anders

HI, A heads up, there was a problem with the builder.io plugin, where it could not do the classic export, and they fixed it in 24 hours - I made a post about it here: Error, Figma: builder.io plugin CLASSIC export in Figma: Only happens when theres an image - Bugs - Builder.io Forum After they fixed it at builder.io I could import again in figma, by the classic export, but not its broken in weweb, BUT to the weweb team, perhaps builder.io made a change in its export and thats causing an issue on your side?

For me, the builder.io plugin works in classic export now, but I get a success message, but no import (I follow the guide, and have been building over 10 pages for the last few weeks with the figma import, and do the same proces as before) - Dear @Slavo and the rest of the team, We LOVE THE FIGMA IMPORT, and its kinda crucial for us to build quickly by importing for clients/future customers, could you please look into it quickly?

Since I discovered the builder.io bug and they made the update, perhaps a small change was made there to the classic export code, and it could affect the weweb import function, or perhaps you just launched a small update?

Best regards, Anders

For testing, I tried to import just an image (the key), using the builder.io, classic export, I got the same success message, but no root container was imported - The image now shows in the weweb image library, so the import from figma in weweb, does actually read and save, but does not import into the page.

and I tried to import the image and just a text string, in a new project, on a blank page, same problem

Checking with our tech team

1 Like

Thanks a lot @Agustin_Carozo - It means a lot to my team and users. they are requesting UI that feels better, and investors told us, that the current thing we have needs a lot of work (due to my bad UI skills) so it is quite important to us, and the import is AAAAWESOME when it works, Can litterally pop out new pages and elements into my dashboard from figma designs i bought in minutes, it saves me weeks of work!

Best regards, Anders

1 Like