Reading all the comments it becomes very clear that XD is a flawed product with no QA and no respect for its users. It is insulting that the users have to vote for a product to work AS IT SHOULD. These are no feature requests, just cries for XD to be made PROPERLY.

An analogy would be having to "feature request" a word processing software for being able to use capital letters.

Seriously?
Should we be requesting for this feature or just fking leave and use a software who's developer's have a bit of common sense.

3 years later and another basic, fundamental feature still hasnt been introduced. Adobe, if you want us to all jump ship and use Figma, please just let us know and put us out of our ongoing misery.

Knowing the very high quality of other Adobe Software it is really strange that after two years still nothing has happened.
It takes hours to repeat every step for every component status. It would be really good to know if something is at least planned. Otherwise this is a showstopper.

Adobe, I am a fan of over 10 years. You make extremely efficient tools for designers and have been leading the industry for quite some time. It's perplexing that this critical issue was escalated 3 years ago and no solution has been implemented. There are too many voices that have already spoken on the burden of editing text for multiple states. What is the hold up? I personally pay for an Adobe subscription (w/ XD) with my own money, while the company I work for uses Figma. On the daily basis, I am using both tools and comparatively Figma has the edge for essential needs like this. Is it fair to ask when will this urgent and important update take place?

This is also an issue on the main component regarding the hover state...

I can't believe how Adobe doesn't get serious on developing XD properly... Preferes to add experimental crap like voice commands and leaves critical things like components states unusable.

This should be a simple enough feature to create. The “default” state should always be the “Master” state, one that controls the content of that instance, then a Name editable first state would be created.

This would still allow a master component to control and change things, via the master state and likewise, changes made to individual states would “unlink” from the master state as it goes now but it would give control to things like text, color, size and even placement on our instances of a component in files.

It’s imperative to add this functionality as using it in the current state completely invalidates creating library components that have any complexity.

Please add this feature ASAP. It makes changing the instances very tedious!

Please add this feature as soon as possible

Hi, another designer here. I'm in struggle town and I'm so over changing every single state for years! What do you need to make this happen?

The absence of this feature is a big downside in the app. Adobe, please improve your product and your users experience.

Adobe does not seem to take prototyping seriously, this feature is super-critical. I fail to believe Adobe uses XD to design their own products yet has not come across this as a major pain point.

It is game changer!!!!

This is a daily struggle for me. I seriously stumble upon this issue at leat 20 times a day, where I have a button that I forget to change the text on the hover state and it messes up my whole prototype and confuses the client....

Since Adobe is not willing to take critical steps towards basic working functionality I'm really angry that I will have to consider Figma at last ... :-/

Still waiting... Can't you just post the code of XD on GitHub? The community then will fix this stuff within hours...

Feature has been under review for almost 2 years. What is there to consider? Not being able to swap assets across all states of an instance at once is such a waste of time.

Just coming back to see if this is still a thing before I make the move to Figma

How on earth is this not a thing yet? It's a simple fix. If you edit the text in the Default state of a main component, it already updates automatically to the other states. Can't you simply make it so that the same applies to component instances? Or at least provide a way to update all states within an instance with a single click?

This isn't rocket science.