Report a Problem

Every time that I create a new component, I have to restart my file to see him appears in the Library research

If the two anchor points of the vector are not connected, then the vector always stays centered even if it selects the inside or outside in the stroke settings. Suppose I have an SVG that’s set to inside. While I try to remove one anchor point, it creates a gap and again makes all the vectors set to center automatically, which is a big problem from my perspective.

Hi, The bug i am experience on the regular is when pages in prototype view jump around when component has auto layout and smart animate applied. I know this is a bug that has been discussed many times on here and has been around for years at this point along with other prototyping bugs. Which is why I wanted to ask why this has not been fixed, it is very frustrating when we get all this amazing updates with great new features but bugs that affect peoples work everyday don’t seem to get any attention. Hope prototyping can get a big revamp soon as we have great tools to build with but can often fall short when it comes to prototyping and presenting to clients.

Previously, when I add a Figma wireframe to a jira ticket via “Add design” button, the jira ticket would automatically appear in “Dev resources”. It seems to no longer do that. Is it a bug? it would be great to get that back as it saves a lot of time and energy, it really adds up.

Trying to reshape a connector from a shape to another connector with text. I can move the connector to the position I want, but once I release it, it snaps back to the starting position…is this a bug or am I missing something?! Connector Snapping|video

I just got the UI3 update and it looks like the distribution buttons have been permanently tucked under an overflow menu now. They’re really useful, though, and I’d love for them to be at the top level of the UI, at least when using the select tool.

resolvedVariableModes is empty if the node doesn’t have at least one variable defined. This is also the case if the parent node has an explicit mode. Expected behavior: According to the documentation, nodes have default mode values, which should be returned regardless whether the node has a variable or not. resolvedVariableModes | Plugin API

I often get a weird blur in the new interface. It isn’t part of content and doesn’t move with the canvas. Reloading the tab remedies this, but it’s really annoying.

I recently published a plugin, and since then, I have been unable to test new updates locally. Changes to the ui.html and code.ts files aren’t reflected in the local Figma plugin. Related: Hot reload not working with React

I’ve applied smart animate to my interactive component. Its got a stroke applied to it with a radius of 16px. Every time it expands and collapses the stroke glitches and pixelates. Any clue what’s causing this? Is it a known bug?

I had a Figma deck where I had used variables to control the component states and I was setting them using actions. I had to merge these views into a larger deck and copied them however none of the variables are appearing in the new decks variable panel or are they available to assign. Where they have been previously used they still appear as assigned variables but cannot be edited etc. How do I migrate the variables?

When you change a nested instance of a component property’s variables, it doesn’t update the change to the lowest level. So you have to click all the way through to ensure there are no breaks in the component and inconsistencies. This somewhat renders the feature moot because you cannot rely on the UI’s tree. You have to fix everything manually

When I select a layer, it scrolls into unexpected place. Every time. This behavior or bug, makes me crazy. How to turn this shit off?

I want to reuse my self-made template, but it doesn’t appear in the templates list. Which is very annoying. What’s the purpose of custom templates when it isn’t made available for yourself/your team? Kinda a turn off to have to open the template first and click the tiny button in the top right to use it elsewhere (for which it has to be updated completely). I also noticed that somehow Figma wants me to update the slide deck template, whilst there were no changes made to it. Is that because of library (design system) updates I made?

When attempting to delete a mode of a colour variable, Figma freezes. This happens for both desktop app and web version. Edit: Can also happen when trying to add a new mode.

I have noticed that, when I’m in design mode, certain settings that normally appear in the right-hand design panel sometimes disappear. It seemed random at first, but today I realized that it’s consistently happening whenever I toggle over to the animation panel and come back to the design panel. Specifically, my corner radius and opacity settings are disappearing. The only way I’ve found to get them back is to right click and refresh the whole file tab. The attached images show a comparison of the panel before and after I change the slide’s animation settings. You can see that the “Appearance” tools have disappeared. Has anyone else encountered this? I also filed a bug report.

Is anyone having any luck with sorting variant properties in this mighty shiny new UI? I am using components with icons that I like to sort using my own logic instead of Figma’s, and no matter how hard I drag them (from the side -yes, I know, I know) they are usually sticky? What in the actual sorting fail is this?? Often times -I genuinely wonder- if anyone from Figma is actually using Figma. This is beyond me, why they did away with the (very) old sorting that was in fact working - old folks will remember the one where variants were a different list with pill-shaped items and you could click anywhere to drag them around. Key word here is around, since if their names were short enough, you could even have two on the same line, and therefore it would take even less space compared to this abomination that in the new UI is not even working anymore. To add insult to injury, Figma is successfully unable to at least link the sorting of the layers with this abomination. Because you know, you

We noticed something strange started happening in Figma with Text Styles. Fonts started too loose its weight and width variables.

I’ve set up a custom keyboard shortcut in Figma for copying as text on my Mac. It was working great, but after the latest update, it’s broken. Please fix this issue as soon as possible. It’s making my work much harder. There are two text layers with different styles I select the first text, press the key combination (control+command+C) I expect that only the text will be copied to the clipboard, without styles (copy as text) in fact, the text with styles is copied macOS 15.0.1 (24A348) Figma Desktop App version 124.5.5

The component picker has always been a bit janky. However, the picker in the new UI is now almost unusable within projects that have many components. What I’m seeing The picker I’m talking about is the one shown when I hit SHIFT+I. I have the following issues with it: Search is painfully slow, sometimes taking up to 30 seconds to load the results In-flight searches prevent continuing to type in the search terms If I don’t type all the keywords in immediately, sometimes an in-flight search while I’m typing will clear new characters typed into the search bar I’ve emphasised the biggest issue I have with the search experience. Here is a short screen recording of the issue: What I expected The search input field is completely isolated from whether or not there is a search in progress. That means I can at least make sure I have the right search terms and wait for the results. This is pretty standard behaviour for a search input.

I downloaded and installed the latest version of Figma for macOS running over the existing installation. The app didn’t launch afterwards. I followed proposed workaround on the forum - mainly clearing Figma cash via Terminal and removing and reinstalling Figma but non of these workarounds helped. This seems to be a common issue…

Some plugins are missing from the search results in Figma, even if you type its full name. For example Styles & Variables Organizer or Noisy Gradients

I’ve been always experiencing this bug since the last update of Figma. I have these input fields with new updates. And these input fields are wrapped with a parent component called Signup Form. And this Signup Form is already used in my projects. Note that the CTAs are separate from the form (wraps all the inputs). Now, if these Input fields have updates, the Signup Form’s prototype will break. This is ready ridiculous. It happens many times. Please! Please! Please! Have a look at this.

This is so weird. Restarting the app didn’t fix it.

Did anyone encountered problem with colors in Figma? Same component, same orange, same hex code in two different files = totally different colors. Both profiles set to Display P3. Why is that?