Report a Problem

Hey, I’m running the current Beta and use some conditionals in my prototypes. For reasons I had to copy the whole prototype to another file. After copy the prototype the conditionals are missing. I used partly two or three conditionals in one action, I guess this is the tricky part. Would be nice to have a fix here. Regards

I have components with variants. When I click a component and then go back text doesn’t update. I selected “Reset component state” but it’s not helping 😦 HELP!!!

I have a design file that uses a library from another file. In this design file I’m using a component from the library — a button with rounded corners — which uses a variable number (30px) for the corner radius. When scaling this component in the design file, initially the corner radius variable is, as expected, being scaled accordingly. However, then it switches back to 30px. Clicking the corner radius back and forth made it go back to the scaled value, but then some components randomly switch back to the default value (see the screenshots).

Hello everyone, looks like after recent Figma API update (August 31, 2023), my plugin stopped working properly. At least that’s my assumption because it worked yesterday without any problem. But based on what I see in the changelog, there are no updates to what is used in the plugin. The issue is that Figma plugin API do not support Reaction.actions as array, only Reaction.action (Reaction | Plugin API), but in development my plugin is now throwing an error: This node contains an action in its Reactions. Please update the actions field instead of the legacy action field in order to prevent potential data loss. Any idea what the problem might be?

we have used variables to style an object in figma (e.g. colors as fill, or numbers as auto layout and radius properties). when copying properties using ctrl+alt+c, its expected to style new object with variables, not static values. but figma uses detached variable values to style new object. This behaves right when using styles, but variables cannot be copied correctly. so its annoying to set each value manually.

Hi there, I’m trying to get xaml code for my Figma design, and always get this error. What can I do?

I feel like variables are such a powerful tool but it’s just not usable yet. I’m having this very simple issue but it’s breaking the experience for me. I’m creating a list of buttons and each button sets lots of variables all at once, but, whenever I copy this buttons and paste into another frame the prototype actions that I set up simply break: I cop

Hey everyone, I’m currently working on a Figma plugin that involves Styles, and I’ve come across an unexpected behavior with the DocumentChangeEvent: I noticed that when a user opens the “+” pop-up in Local Styles to create a new style, clicking on any style type triggers the DocumentChangeEvent with all three possible style changes (create, delete, property change) at once. However, at this point, nothing is actually created, deleted, or modified, so the user is notified about changes that didn’t happen. Is there a way to work around it? I want to avoid notifying users about changes that haven’t taken place yet. Thanks in advance.

I want to create show hide shadows and other effects using Boolean variables but right clicking on the eye icon I am not getting the variable lists in Effects property panel… Kindly fix this ASAP

Take the example of a frame that contains a list of items, where the first item in the list is a main component, and the rest of the items are instances of that component. If you duplicate this parent frame via the UI, the list in the new frame will be all instances that point back to the main component in the original parent frame. The documentation for FrameNode.clone seems to say that it works the same way: “Nested components will be cloned as instances who master is the original component.” However, what I am seeing is that clone instead creates a new main component in the new frame and updates the instances in the list to point to this new main component. Ironically this is the behavior I wanted and was writing a plugin to do the same thing. But it is confusing that the documentation and behavior for clone do not match. Has anyone else encountered this?

1. Describe the bug/issue you’re running into? Typing an accented letter in Mac OS can be done by keeping a keyboard letter pressed which reveals a range of accents. 2. Are you able to consistently reproduce it? If so what are the steps? Open Figjam on a mac, type into a note, long press E, and try to insert an accented letter (e.g. é). 3. Share a screenshot, recording, console log, link to the file, etc.

impossible to set “if” and “else” conditions when changing the state

In this example, List will get different props.children value. And here are my codes: const { AutoLayout, Text } = figma.widget; function List(props: any) { console.log('List children length', props.children.length, props.children); return <AutoLayout name={props.name}>{props.children}</AutoLayout>; } export function MenuUsage() { return ( <AutoLa

I’m getting a weird bug, i’m using createImageAsync within a widget (placed in Figma, not FigJam) and loading an external image. after browsing docs and changing the manifest to contain ‘allowDomains’… it still doesn’t work. the weird part is looking at the console I can see the image loaded correctly. in the code I’m using async/await within try/catch… but no error is thrown out. any suggestions? piece of the code below Network tab in console

When I use the color selections on a text item with multiple text, it just doesn’t work

I’ve been trying with no success to use “Set variable” interactions with variants. I have a simple chip component with Default, Hover, Active and Selected states. When clicking it, i want to toggle the right chip visibility to “true”.

Devmode beta: It’s missing the font weight property while regularly, you’d see all text properties.

Hello everyone, I wanted to share a problem I’ve been facing with a button component that has variables applied to it. The issue arises when I try to change an instance’s size property. Instead of resizing to the predefined values set in the component, the button glitches and resizes to a different size altogether. However, when I remove the applied variables from the components, the instances behave normally. Has anyone else encountered a similar problem?

1. Describe the bug/issue you’re running into? I have been granted permissions to edit, both from the team I belong to and specifically for my account. I am not able to edit, I’m stuck in view-only mode. All of my team members can edit. This issue is the same in-browser and in the desktop app. 2. Are you able to consistently reproduce it? If so what are the steps? Go to the file: https://www.figma.com/file/pJPdWYHhzUFZNBBjSKsJMI/Brand-Refresh-Component-Update?node-id=0%3A1 Be signed in as me: [email redacted] Attempt to edit. 3. Share a screenshot, recording, console log, link to the file, etc.

I am trying to add a function to a widget I am currently developing that changes the width of text with the touch of a button. I have implemented this so that the width of the text is held in a variable using useSyncedState and can be switched between a fixed value and “hug-content”. If width is a fixed value, it works as expected, but when switching from a fixed value to “hug-content”, it is not reflected in the width of the Text layer. Here is the sample code. const { widget } = figma const { useSyncedState, AutoLayout, Text} = widget function Widget() { const [textWidth, setTextWidth] = useSyncedState<WidgetJSX.AutolayoutSize>('textWidth', 'hug-contents') return ( <AutoLayout direction="vertical" > <Text fill={"#cc0000"} onClick={() => { if(textWidth === 'hug-contents'){ setTextWidth(300) }else{ setTextWidth('hug-contents')

I’ve recently started using variables for prototypes and I noticed that when variable is set after an interaction it is breaking my text styling. In the design file, I am using a bold typeface but after the interaction it changes to a lighter one. Has anyone seen this? any solutions?

So the thing in a topic name. The video as an evidence As soon as i put the component into frame in stop sync.

Cannot merge or update branch. I only got the message »Error occured«. This error occurs if I want to update the branch from the original and if I want to merge the branch into the main file.

I’m sure the variables settings that i removed came back after i restarted Figma application. I tested it multiple times. lets say I have a flow with 15 frames, the variables settings came back in the first 2-4 frames. I’m not sure what is wrong.

Hello! While doing some discovery work on publishing Variables from a library I stumbled onto quite the bug. This bug involves Styles, Variables, and the ability to change a Style definition outside of the publishing file. It’s a doozie! I have included a video below showing how to replicate the issue.