I started to switch from heavy Photoshop interface mockups to XD and this feature request is a major blocker.

For example our designs have many instances of repeating colors: a white background and a white text. They can't share the same global color as the background might be edited to grey and we want the text to remain white.

Please Adobe allow us to duplicate color assets and assign them unique names and values.

I curse XD daily and nightly. And am scared to update any libraries incase hours and hours and hours of complex work is unravelled with one click. These fears and the many problems I experience with XD were never part of my experience when using Figma.
I believe there is a huge price difference between the two products. You do get what you pay for. And maybe XD wouldn't be bad for simple projects.

I'm getting really sick of the limitations in adobe XD. I don't believe that Adobe XD is suitable for users who need to build complex components and work on a Design System. This idea was shared in 2018, it is now 2022! I'm wasting so much precious time on this bullshit. I've been patient, but now it's time to switch to Figma.

I agree. Developer need meaningful names to color styles. For that duplicate colours might have different titles. It also implies objects will be associated with named colour styles. So it will be helpful to developers also and designers can experiment with colors with different names.

We are in 2022 now and this basic functionality needed for design systems is still not implemented?

This feature would save me so much time! A way this could work would be to add a checkbox either globally or when right-clicking certain assets.

It would be great if a color could be created as two different color styles. Two elements such as button and link could have the same color but different names as far as the color style is concerned.

This should be a basic possibility. Mind is baffled that Adobe XD doesn't support this.

This basic feature being still not available is very annoying...

In my case, BackgroundHover and BackgroundSelected are the same color, but I still want them to be logically separated in the design tokens

Is this still a thing, why would this not be fixed when they announced design tokens? It's useless to have tokens if you can't actually use tokens because one instance of a color is allowed. Not to mention it destroys the ability to change a color by token for fast updates.

This feature was in the previous version? I have never seen this BUG but now I can no longer manage my main library which is the basis of all my professional projects ... I'm starting to get really angry with Adobe xd.
We can't managed design system with this bug...

Having duplicate colors and type should be allowed. Allows more fine tuning if you use them as variables.

Oh, Yes, Please! The same goes for text styles! I work on an document that has a light scheme and a dark scheme. So a distinct color may be used in two different contexts. But I cannot generate a full color palette, because XD merges some swatches. At the moment I define one color with a on-digit change in the Hex Value listing #CCCCCC and CCCCCB. That ist in no way professional.

it's hard to manage when you use one color for several proposals and you want to duplicate it. For example:
I have a group of the primary bench of color and one group for the charts. I cannot duplicate the primary one inside the chart.
It's an issue because I have to create a wrong color code and give the right name and be sure the Front-end team knows which color to use...
How to lose your time

This is a big annoyance for me too, the ability to turn this off would help when testing different colors.

Example: I'm testing different shades of a color and comparing to another symbol. I accidentally overlap the colors and now different sets of objects are linked to the same asset color.

A pretty foundational logic gap that you can't develop a design system that isn't built upon function-based organization. Let me decide how I want to manage my colors instead of assuming for me. It's also incredibly frustrating that every competitor software and all other Adobe programs allow you to work this way, but for some reason XD is different.

It's really unfortunate that my team is handcuffed to Illustrator because XD can't do so many basic things that designers need and we can't realistically buy licenses for other software for the whole team on top of CC.

You can consider the following case to find out how much it is annoying. I want to have two colors: 'Text on secondary' and 'Text on surface'. Currently, I have a light theme with a light secondary color, so both of these assets are black. But after a while, we may decide to change our color theme in which our text on secondary color would be white.
Colors will be totally mixed up just because those have been merged.

Please consider implementing this. It's a huge pain for us at the moment. I would love to be able to define colour assets by function (background, dark background, button, dark button, header, dark header, etc.) but in some cases I use the same colour for different functions. It's not possible to achieve this with the current implementation.

It's also a problem for defining light/dark mode colours. I could define a colour (Blue) and a dark mode equivalent (Blue Dark), but it's not always the case that everything that uses blue in light mode will use the equivalent dark blue in dark mode. Different elements may need a different treatment, and it becomes messy to keep track of this and communicate to developers.

This is a real pain for us too. Can anyone from Adobe provide feedback please?

It's September 2019 and this issue is still not resolved. Anyone at Adobe looking here?
I'm currently working on a project where I have hundreds of colors for some elements (each element has multiple states and children that also have states)

Now I'm creating the assets palette and I have to play the 5000 shades of grey in order to be able to create a colour asset for each state. then, If after I apply them if I change a colour and mistakenly matches an existing #hex in the assets panel, it destroys one of them.

Any hope of getting this fixed?