Report a Problem

Hey, I find the compare changes to previous versions incredibly valuable BUT I’ve noticed some inconsistencies that holds me back with recommending that to the whole team 😉 If I inspect frames marked as Ready for dev in that new Overview page for developers the available history ends on the first event of marking that frame as Ready for dev BUT if I go into Compare changes mode of the very same frame directly from the design page (meaning not visiting that Overview page) I can see states since the frame got created PRIOR marking that frame as ready for dev the first time. I would be interested in being able to compare changes back to the creation of a frame no matter of how I access the comparison view.

Why is it that every once in a while, I will open my assets panel and every single asset group in every attached library is fully expanded? Why does Figma not put together menuing like they are run by UX people? 🤬 </rant>

I’m trying to use the bold/italic command in FigJam and it just doesn’t work. I have tried restarting Figam and my computer and neither worked. I have also tried both in shapes and in post its.

Hi! To cut to the chase, we have a main project where we’ve created our Design System using Local Variables. These Local Variables were then published as a library to use in other projects, however, when adding this library to another project, no collections show up in the Local Variables panel. I have checked and all variables have the “Hide from publishing” option disabled. To add insult to injury, they do actually show up in the Library panel but that’s it. Different Variable collections that were published: Same library added to another project: The Local Variables panel is empty but somehow the project has access to modes, even if the variables themselves are not available anywhere. What can we do?

My team is having some problems pulling some components out of the library. It is not all components, though. We get the following error: “Unable to load. Something went wrong. Try closing this window and reselecting the component.” Closing the window and reopening does NOT fix the problem. I have done to following so far to try and fix the issue: Checked the component in the component file. No errors here. Republished the component. Did not fix the issue. Unpublished the entire library and republished. Did not fix the issue. Note: I was able to publish with no issues. I’m at a loss and not sure what to do.

Dont know is it bug or not, but atom component size is not changing inside of molecule component asset. Scenario: we have component “Btn” with 2 variant sizes (atom component) we have component “Btn Group” with 3 Btn assets in autolayout (molecule component) Mission Failed: Usage of asset “Btn Group” component where I want to change size of 3rd Btn Asset… Style (color) is changing, but size is fixed as master component setup If we use autolayout without component “Btn group” resize is working. Any help? Is it bug?

The design file is still there, but the design draft inside disappeared yesterday, and only the records from seven days ago remain in the historical records and cannot be retrieved. Can you help restore the last version from yesterday? Figma – 15 Oct 24

The export type incorrectly retains the suffix, after I change the format. Steps to reproduce: Create a simple shape or rectangle layer Hit the “+” next to Export 3 times. By default, this will set the exports as follows: 3x PNG with suffix “@3x” 2x PNG with suffix “@2x” 1x PNG with no suffix For the 3x PNG, use the dropdown to change the format to SVG. Open the “…” overflow menu and observe that the suffix is still “@3x”. Expected: When I change the format from PNG to SVG, the suffix field should reset. Relevant docs:Figma Learn - Help Center

Hey everyone, we have a custom solution that pulls our variables directly from Figma into code. It works by identifying each variable through code syntax and distributing it based on the platform (iOS, Android, Web). We encountered an issue where a specific variable appears as a duplicate. The problem is that this repeated variable doesn’t actually exist as a duplicate in Figma—there is only one instance. We’re using a plugin called Heron Variables that processes all variables, applying code syntax for each one based on its name and platform as defined. Here’s the output from our developers: ... 'Component/Button Text/Tertiary/Default', 'Component/Button Text/Tertiary/Hover', 'Component/Button Text/Tertiary/Pressed', --------------------------------------------- 'Component/Button Text/On Color/Text', 'Component/Button Text/On Color/Text', <- AGAIN --------------------------------------------- 'Component/Button Text Navigation/Text' <- NEXT TOKEN ... As you can see in

I believe I am experiencing a bug, but I am wondering if there is something I am doing wrong. I have an app prototype that opens a donation bottom sheet as an overlay. On that overlay, I have input chips to quick-select a donation amount. On those input chips, I have the interactions set to on tap - set variable DonationAmt to a specified string then change to a variant I created with that input chip selected. I put the set variable step first otherwise there is a small delay in that variable populating into a text field due to the smart animation on the input chip selected state. The issue I am experiencing is that the on-tap event for the component on the overlay frame is not working. This is only happening when viewing the prototype on the browser. It works as expected on the mobile app. On the browser, it’s as if the click is interpreted as a drag. That single click is functioning like a held down click. The input chip state doesn’t change, and the variable is not set. It instead

I’m using the Metric font, and trying to align text, using auto layout, but can’t do this because the baseline for different weights shifts, so different weights of the font won’t line up correctly. I checked in Sketch to see if it’s a problem with the font in general, but it seems to be fine there. Can someone please look at this? Thanks!

After installing Figma, I was able to use it normally. However, after I closed Figma yesterday and reopened it today, I found that all the installed fonts were gone, and my colleague experienced the same issue. We’ve tried reinstalling Figma Agent, restarting Figma, and various other solutions, but the problem still can’t be resolved.

Hi Figma Team, I’m experiencing significant performance issues with the native Figma app on Windows x86. When running Figma on my Surface Studio Laptop 2, the application seems to underutilize system resources, barely tapping into the available CPU and GPU power. This results in noticeably slow and laggy performance, impacting usability. Interestingly, Figma runs much smoother in the Edge browser, where it also makes better use of the Intel GPU, providing a more seamless experience. In contrast, the native Windows x86 version struggles with basic responsiveness. Could someone from the team look into optimizing the native app’s performance, especially regarding GPU utilization? It would make a big difference for users on x86-based systems. Thanks for your attention to this!

Hi, I am posting this bug in interactive components because it never happened to me before I joined the beta and can’t seem to find any topic similar to this one. The issue is quite straight forward. When I create a component (without interactive stuff inside) in a project that has interactive components beta, and try to change the text style from a library style to 1 of the text inside the instance of that component, the text style changes to a random one, that is NOT part of the library. To give an example: I created a component. I went to an instance and selected a text layer. Then went to my library’s text styles and clicked on one (H4 in this example, which is 28px height with 114% spacing): As a result, it applied a random styling… not from the library. It applied a bold 22.4px style??? I think it is related to this beta… unless someone tells me they got this same issue before.

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?