Report a Problem

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

Whenever we have a branch open from a main file and are doing work, we are constantly getting updates that the branch is different from the main file. This is to be expected, as I am working in the branch, but this is persistent and never goes away. The moment I start making changes in a branch, I am presented with a dialog stating there are changes in the main file, even if it hasn’t been touched. Then if I click Update and Keep Main, I will end up overwriting all of the work that has been done on the branch. Not sure why this is happening, but it is certainly frustrating as it negates the whole point of a branch.

If you change the name of the instance by calling the rename function, the documentchange event will fire and indicate that the name property has been changed, but if you undo/redo, this event will not fire. Steps to reproduce: Place an instance of any component on the canvas, or select an existing one. Run the plugin with the documentchange event listener. figma.on( 'documentchange', ({documentChanges}) => { console.log(documentChanges) } ); Change the name of the selected instance using Figma’s native rename function. Undo and redo the last action. Expected result: The documentchange event will fire and print an array of objects to the console. Actual result: The documentchange event does not fire.

If you have some problems with changing color while using variants in Figma, Here is a solution: All in all, you need to Flatten each layer of a variant, for this, as you know Figma doesn’t have the Flatten each layer option, so I suggest you download the Automator plugin. After that, Select all layers (you can do this by pressing Enter while selecting the parent layer) Run Automator > Object > Flatten selection, then click Flatten each layer. Done!

When I have plugin panel open such as “Tokens Studio”, opened submenu is overlapped by plugin. Problem is that I can not have them on the side as overlapping submenus.

I am trying to change the image But I can’t choose image

Form input values become unresponsive on reopening of app after closing it from the plugin API figma.closePlugin(). Well it works fine when we reopen after closing it from inbuilt plugin ‘X’ icon placed the top right corner.

When i click publish plugin button, nothing happened. Some error info shows in dev tools.

I had a component with that had a Color Style layered in this manner: Image Layer (85% opacity) – just the Figma’s native placeholder checkered background #858585 Solid Layer (beneath Image) I recently updated this Color Style and added an image to replace the placeholder checkered version. When I publish the update and update my component instance on a separate file, the error “An invalid image or thumbnail was removed.” For now, I’ve been able to avoid this error by layering the Color Style in this manner: Image Layer (0% opacity) – the original checkered background image layer New Image Layer (85% opacity) – the image I intended to replace the placeholder #858585 Solid Layer Is there a way to fix this issue so that I don’t need to layer redundant image layers? Thanks!

I was working on a branch and was at a point I needed to update the branch with recent updates from the main file. When resolving the conflict between main & branch (it was the only conflict and was an entire Section that I had been working on in the branch) I chose Keep Branch, it kept everything as expected EXCEPT for all the arrow styles on lines that I had updated in that Section. I noticed the arrows weren’t displaying correctly in the branch window when viewing the conflict side-by-side, even though they were clearly a different style in the branch itself.

In my colour library “Light Theme” I have a colour style called “contentDefault” if I create a rectangle in the library, apply this style and then run figma.currentPage.selection[0].fillStyleId I get the fill style ID S:1eab1fd8b8857bf87c862afd0590934a23ac0368, (key changed). If I run figma.getLocalPaintStyles() I can see this same key appears as a local paint style in my library. The library is published and up to date. In a separate local file I have 2 different text elements and they both have the style “contentDefault” applied to them, but when I run figma.currentPage.selection[0].fillStyleId they have two different values: One is S:1eab1fd8b8857bf87c862afd0590934a23ac0368,15:73 while the other is S:effba5ca507e1ec8b0b745807cfb2da2e0c3fcdb,2398:0. If I open the colour style selector it indicates that both of these styles are “contentDefault” and both are in the “Light theme” librar

Documentation for this feature is here figma.com but when I try to use it, I get this error figma.createImageAsync is not a function Even in the app I get the same error Thanks!

Hi I thought this was a missing thing in Figma but it seems it’s not working in Windows only. For instance… SHIFT + 0 SHIFT + 1 SHIFT + 2 It’s very useful and more productive to have them. Thanks