After latest update, components in design system are broken size/scale wise.

Not only is this happening in instances of component using SVG icons, but similar to last months break.

1- Any instance overrides are being reset when i change a variant property 
eg, set a text input instance to fill in an auto-layout group -  Then change its state to “focused” and the master component fixed width value is applied

2- I duplicate any frame containing items with auto-layout overrides on instance and all size value are re-set to the initial master value

 

Same issue here. The components are totally fine within the designsystem file but icons with constraints are not scaled correctly when copy-pasted to a design file or added from the asset library. 
Strange thing is that detaching the component makes the icon scale as intended.

Seems like the scaling constraints are completely off at the moment …
 

By the way: I tried the “regenerate all instances” trick mentioned earlier in this thread. It worked on the first file but not on the second and the third 🫣

 ​@Stein Olav Pettersen lucky you! After clicking on the icons (usually, in some cases just clicking on them would help me scale them to the intended position) I would run regenerate all instances and all the icons would break the scale again 😓

​@Alex172 Thought I managed to make a fix by wrapping the icon in a frame (just adding complexity to the component so kind of stupid …). But It worked for all instances except for one. Decided to try and regenerate all instances and hoped for the best. Guess what happened … All instances broke except one 🫣

 

​@Stein Olav Pettersen as of now I have not found any valid workaround… Did not test the component refactoring and am trying to avoid doing this as much as possible.

Just halted my main tasks and waiting for ​@djv and her team to fix the bug..

​@djv I have shared a file with support-share@figma.com as well. I can’t work safely or share my files until this is fixed.

Hi ​@Alex172, thanks for letting me know! 

I located your ticket #1623940 from Tuesday, and Ben from our technical quality team replied to you earlier today. Can you please confirm that you’ve already shared support-share@figma.com as an editor to your file? 

It looks like he tried to access it, and he was unsuccessful. Feel free to also respond to him directly via email for one-on-one support in the interim. 

Hi ​@brc, thanks for chiming in here! 

I located your ticket #1628019, and it looks like you actually didn’t share a file with us stating “Everyone has this issue, you don't need a URL from me.”

For future bug reports, having an individual file is incredibly helpful. Even when many people are experiencing something similar, bugs can show up differently from user to user, so the unique details are often what help our team identify the root cause more quickly and accurately.
 

That said, the team does have this entire forum thread of screenshots and Alex’s file to reproduce the behavior, so they’re actively looking into it. I’ll make sure to provide an update here as soon as we hear more from them.
 

Thanks again for your patience and for bringing more visibility to the issue.

​@djv My apologies, per the earlier comment I thought that adding support-share@figma.com as an editor to the file was sufficient. Thank you for the updates.

No worries, @brc!

Just to clarify, support-share is a shared account our support and product teams use so they can review user files without adding extra Full seats to your team. Invite support-share@figma.com as an editor was correct. But on our side, we still need the direct file link. Since support-share is a shared handle used by multiple team members, the link ensures we’re looking at the correct file you’re referring to. Thanks again for your patience while we work through this!

​@djv please add my ticket number #1626019 to the same issue. I added links but I have done some refactoring since then (added extra wrapper layers to the icons which should not have been necessary).

Please contact me as soon as possible if I can be of any help solving this issue. The only replies on my ticket are my own …

Hi, ​@djv I have shared my file to support-share@figma.com. Please add my ticket number to the same issue #1629429. Apologize for the late reply and thank you in advance.

Hey All, thank you so much for your cooperation and patience while our team worked through this bug! 

The team just pushed a fix for this. Can you please refresh your tabs and try regenerating all instances again? 

Please let us know if you’re still running into issues. 

Hi ​@djv 
Did some testing here. All seems to be fine on my side. Also restored our asset library to the version before this happened to remove the extra wrappers I added as a workaround. The assets work in all sizing modes now without breaking the constraints. Thank you for prioritizing this issue 🙌. Last week was rather frustrating 😅

Hi ​@djv I confirm what ​@Stein Olav Pettersen has shared, everything is working fine now.

Glad to hear it, ​@Stein Olav Pettersen & ​@Alex172!

Please do loop me in here, if you run into any further issues.

Hi again ​@djv, 
Similar constraint issues are unfortunately back. It happens when changing size-modes according to our token/variable structure. These are all instances from the same main component but the behavior is not consistent.
Weird thing is that the effect is pretty random as you can see from this example - and it seems to move around. Made a quicktime recording just a few minutes ago - then two other instances resized the wrong way.

Been running the regenerate action but no success so far …
 

Screenshot from recent quicktime recording:

Added another test with more instances to try and find a pattern but it’s still awkwardly random. Within the main component the size modes works perfectly fine. It all happens on the instances.

Before changing size mode (default medium size):
 

After changing to large size mode:

And after a while where I switched from medium to small to large size mode. Notice the difference in size-patterns from the screenshots right above here ☝️:

Also just found that the Regenerate instance action only work when using the default (medium) size mode.

 

Hi ​@Stein Olav Pettersen, thanks for letting me know! 

Was this working for you as expected earlier this month? And if so, when did you first notice this happening again? 

Is this happening in both the desktop app and the browser? And are they both up to date? Lastly, is this happening for all your files or just this file in particular? 

With a few more details, I can flag this over to our team to see if anything has changed since we pushed the fix. 

Hi ​@djv, it was working as expected earlier this month - and still works fine with the files where I had issues before. This is a new component I am working on and the issue seems to be only in my branch (so far …). This is happening both in the desktop app and the browser which are up to date.

Reported the issue to the support team and will send a screen recording and invite them in to the file.
 

Hi again ​@djv. Just a short update: The Figma engineering team has now updated this bug. Appreciating prioritizing this one - now it’s all smiles (correct in all sizing modes) 🤩