Report a Problem

Every time I try to use figma plugins, I always get the circle wheel. It made it unusable and have to restart every time.

My file suddenly started to show an a different component on the live file from the one on the library. the library contains - radio button group and the file shows - accordion single the library looks fine i dont understand what is happening 🤯

There is a fairly big difference in the behavior of getting the publish status of a component in a team library when you use .getPublishStatusAsync vs figma.importComponentByKeyAsync when you are in the main file and then when you use the same inside a branch. I want to ask if this is intended behavior, or if they are meant to be functionally the same? The documentation for .getPublishStatusAsync here says that it “Gets the status of this style/component in the team library.” with no mention that the behavior is different if you’re in a branch or not. What happens in a main file: When a published component is called in the API with the method on the node .getPublishStatusAsync, the code returns “CURRENT” What happens in a branch: The node returns “U

My smaller figma files are loading normally but the little bigger files are stuck on the loading screen. They loaded within around 10 seconds now it’s been an hour now it finally loaded but its still taking too long to load them.

I’m failing to access the navigator.clipboard object and noticed what the title says. Is there a workaround for it? The clipboard is not the only feature we are missing. Thank you.

At the moment there is no functionality to copy a branch from an already created branch. This functionality is very much needed for full-fledged work in branches. Since it often happens that you need to copy a branch with an already created design and make changes to the new branch. Will there be this functionality? At the moment when you change variants or a master component in the master file, this component is reset to zero in all branches when you update the branch. This is a strange solution since all branches are copies of the master file, like working with parent components and its copies in the same file. Changing the paddings inside the master component should not reset borders radius or color style settings. But at the moment it does. Using branches for design copies with variations becomes useless in branches because when you update a branch to the actual components from the master file, all the settings of the modified components are reset. Wi

When I Update a variantPreformatted text on the design system file, it won’t update the child files. Even if I create a new variant, it won’t show on the option of the file, and I need to import it to the file specific

Why I can’t stick line to any point of one object? Only 4 points (up, down, right and left). I need to connect lots of lines to object but they all go to one points and that’s look bad. In instruction is said To place the end point of a line on any part of an object (and avoid the snapping the line to the side of the object), hold down ⌘ Command (Mac) or Ctrl (Windows) while moving the line. But it doesn’t work for me

The plugins where few hours back, but it suddenly shows “Unable to run plugin in this file” now. I already restarted, cleared cache and done everything. Still not working.

I’m getting this error when changing the status of a variant from true to false with the setProperties function `Uncaught Error: “Unexpected: _dirty” in ~SymbolOverrider (FGSymbolOverrider.cpp) Uncaught Error: “Unexpected: scene()->mutationsAreDisallowed()” in set (FGNode.cpp) Uncaught Error: “It shouldn’t even be possible for a read-only scene graph observer to recurse.” in handleObserverEvent (FGSceneGraphEvent.h) ` My code is like this [image]

Boolean operations glitch ? I have a bug when I try to do a boolean operation, my objects disappear. The objects that disappear are not the same according to their position in the group. Here is an illustration:

I use drop event to receive data from plugin and create component in figma, it works fine in figma app but not in browser. figma.on('drop', event => { const { items, node } = event if (items.length > 0 && items[0].type === 'text/json') { const data = JSON.parse(items[0].data) as IconData const instance = newIconFromData(data) instance.x = event.x instance.y = event.y // not all nodes have appendChild method ;(node as PageNode | FrameNode | GroupNode | SectionNode).appendChild(instance) figma.currentPage.selection = [instance] return false } return true }) I also tested on Material-Symbols and it doesn’t drop properly in browser too. My os version is macos 13.2 and browser verison is chrome 110, and there’s no error message in console after I drop. Any ide

The organization version I am using is suddenly unable to pull branches for the entire team today. It was normal before this, I checked all the settings without any changes, is this a BUG? Or is this a result of a Figma update? Prompt that I do not have permission when pulling a branch? The editing permission under My Organization is already enabled. I don’t know what is the reason, does anyone know?

Edit description button after a branch has been merged goes away too fast. I don’t even have time to click on it.

“SyntaxError: invalid regular expression flags” when building a RegExp with ‘d’ flag. Other flags work fine, I use flags “/gid” together. I need to get indices of all matched substrings.

I’m trying to use the exportAsync function to export a Figma node as an SVG file in my plugin. When I use await, the function returns the SVG code as a string, but when I use .then(), it returns a Uint8Array object instead. After some investigation, I realized that the exportAsync function returns a Uint8Array object representing the binary data of the exported file. When I use await, the Uint8Array object is automatically converted to a string using the default character encoding, but when I use .then(), I need to manually convert the Uint8Array to a string. I suggest that the exportAsync function should always return the SVG code as a string, regardless of whether it’s used with await or .then(). This would make the API more consistent and easier to use. In the meantime, I found a workaround fo

Since I have first use Figma, the plugins page does not scroll on safari when using a scroll wheel on a mouse. I have to grab the scrollbar and scroll to have the ability to scroll on the plugins page.

My library don’t publish any update : new component or change… I already try to : Restart Figma and my computer Turn off/on the connecting library with all my files Clear the figma cache It’s really dramatic at this stage of the project… someone can help me? @Figma_Support 🙏

Hey, we recently launched a plugin for FigJam (https://www.figma.com/community/plugin/1220696620350131525) that exports notes as Stickies and clips as Embeds. This works fine for Figma Desktop App but doesn’t replicate same behaviour on Figma on web. We have followed the official guide for implementing drag and drop for self-hosted UI. Guide: https://www.figma.com/plugin-docs/creating-ui/#drop-events-from-a-non-null-origin-iframe Official Code Example: https://github.com/figma/plugin-samples/blob/master/icon-drag-and-drop-hosted/index.html We’re now left with the following doubts Is it n

When I create svg nodes in figma.createNodeFromSvg, two different style nodes were create. However, these svgs have same style in browser. The only code diff were linearGradient x1,y1,x2,y2 as fellow image. It seems like Figma can not handle percentage type linearGradient right？ linearGradient with percentage type x1,x2,y1y2 in browser

I create a variable: let iconVectorPaths : VectorPaths = []; I assign a path (pasted from copied Chrome inspector object): iconVectorPaths = [ { "windingRule": "NONZERO", "data": "M 4.989105701446533 6.993822125878069e-7 L 5.989105701446533 6.993822125878069e-7 L 5.989105701446533 16.013992309570312 L 4.989105701446533 16.013992309570312 L 4.989105701446533 6.993822125878069e-7 Z" }, { "windingRule": "NONZERO", "data": "M 16 5.024010181427002 L 16 6.024010181427002 L 2.1366776081777061e-7 6.024009704589844 L 2.636236331454711e-7 5.024009704589844 L 16 5.024010181427002 Z" }, ... And then later assign it to a variable of type VectorNode: iconVector.vectorPaths = iconVectorPaths; This last assignment concatenates values of many data: attributes of the original into every data: attribute of the VectorNode’s vectorPaths array. Why?

I’m working in a branch and have made a lot of edits. Normally I update from main every now and then to get things up to date and to get rid of the popup, but when I did it today I see that the page I’m working on is changed when opening the dialog. The preview in “Keep branch” is reflecting this and showing me an older version. In the background I can see that the view shifts into the “Version history” view which is very strange. It’s driving me mad. Please help

Sometimes when I add a new component and go to publish the change, the library file shows that it is up-to-date and there are no updates. I cannot copy + paste these components where they need to go either (the linking breaks). Occasionally, entire pages full of components become unlinked and do not appear in other files.

It seems that I have created two rectangles with exactly the same style property, but they look different. Even copying & pasting the style can’t solve this problem.

When I use the example in waitForTask doc the widget doesn’t stop rendering const { widget } = figma const { Text, useEffect, waitForTask, useSyncedState } = widget function WaitForTaskExample() { const [textContent, setTextContent] = useSyncedState("text", "Initial") useEffect(() => { waitForTask(new Promise(resolve => { // Simulate async work setTimeout(() => { setTextContent("Final") // Resolve the task resolve() }, 1000) })) }) return <Text>{textContent}</Text> } widget.register(WaitForTaskExample) On the setTextContent the widget seems to restart and rendering again and again