Until today, I’ve never run into an issue with exports doing this and my components have been named this way in bulk for several years. Is there a way to fix this issue?
Best answer by Tom Reem
Hi again @heyhankhowsthebank, thank you. Great catch on isolating it to Cmd+Shift+E versus the sidebar Export menu.
Those are two different export paths: The sidebar applies your export settings to what you've currently selected, while Cmd+Shift+E opens the bulk Export modal, which gathers every object on the page with an export setting applied. A difference in behavior between them isn't surprising in itself, but the leading and trailing spaces do not appear to be expected.
I tried reproducing this in a test file of my own and the names came out unchanged, which tells me something specific to your file may be involved. It would really help to get eyes on it directly.
I've opened a case on your behalf with our Customer Support team. Your case number is: 2077371 — please check your inbox for a message from me with next steps on sharing the file securely.
Hey @heyhankhowsthebank, welcome to Figma Forum! Thanks for flagging this — the before/after you included is very helpful here.
I checked for other reports of this and haven't found any matching what you're seeing, so I'd like to narrow it down with you.
A few questions:
Does this happen across all your files, or only in one?
Are you on the Figma Desktop App, a browser, or both? If desktop, which version and OS are you running?
If you create a brand new component named exactly Documentation / 1A. Screen Example and export it, do you get the same result or does it export as expected?
That last one is will be useful, especially since it separates a change in export behavior from anything that may have happened to the component names themselves.
If that doesn't clear it up, it would help for our team to look at the file where this started. You can submit a bug report through the Support Hub — type “report a bug”in the tell us about your issue field, describe what you've posted here, and include the URL of the impacted file. You'll also want to share that file with support-share@figma.com with view access so we can reproduce it. You won't be charged for the additional editor.
Hope this helps move things forward. Please keep me posted on how it’s going.
The behavior was consistent from desktop and browser and across my files, but now I’m no longer experiencing it from “Documentation / 1A. Example” but am experiencing it with various other components using a similar naming scheme. “Errors / 1A. Example” and “Email / 1A. Example” triggered it, but then when I edited one of the components, it began exporting properly again. And if I create new components or frames to export, they export correctly.
These components’ names have remained consistent (and many unedited) for years. Any thoughts as to why it might be exporting inconsistently now?
Oh, this is still occurring across more files as described. Only one file seems to be able to export correctly. Components that are part of a library that are named in this manner seem to still be exporting with the leading/trailing spaces.
Hi again @heyhankhowsthebank, thank you. Great catch on isolating it to Cmd+Shift+E versus the sidebar Export menu.
Those are two different export paths: The sidebar applies your export settings to what you've currently selected, while Cmd+Shift+E opens the bulk Export modal, which gathers every object on the page with an export setting applied. A difference in behavior between them isn't surprising in itself, but the leading and trailing spaces do not appear to be expected.
I tried reproducing this in a test file of my own and the names came out unchanged, which tells me something specific to your file may be involved. It would really help to get eyes on it directly.
I've opened a case on your behalf with our Customer Support team. Your case number is: 2077371 — please check your inbox for a message from me with next steps on sharing the file securely.
