XD : Unable to Update Library through update button in XD

I'm having the same issue 2.5 years later. Its sad to see Adobe prioritizes its bug fixes so low that they are never addressed and a sub-par products continues to be sub-par. 

Not sure if this is the same issue I had. I tried updating a CC library from Adobe XD and could not. What worked for me was uninstalling all Adobe programs and Adobe Cloud program using cc cleaner tool.

Then reinstalling Adobe Clound and installing Adobe XD again. I think the cc cleaner tool does a lot so if you use it use it at your own risk. It removes all adobe files I think so if you have work you want saved I would make sure it is backed up. 

I am also experiencing this issue. It has completely broken my workflow and now I am unable to continue building our atomic design system and have to just copy and paste components. So dissapointing that this issue has not been addressed in over two years. 

Faced this issue today.

Here is my solutiuon:

• Browse library file versions history and find a stable one (with updates possible)
• Open that file and publish it as a library
• You will be asked to replace all components from your currently published library
• Agree and then update linked components from library in working files

Thanks God this proccess is automatical.

I still have a blue notification at the bottom after every update. Looks like that happened earlier.

For Adobe, maybe this will be helpfull:

Before that happened, I tried to update quite an old component in my current library. Since that version of XD where hover states were introduced.

You should consider investigation since with an atomic design approach and the number of components – this will become a nightmare. 

Same issue here.

I don't have nested libraries. Just one library and when I try to update any of the components nothing happens. The changes are saved, but the files that use the library do not update them.

In addition, the notification that I need to update the library does not go away.

For me the issue has been going on for years, and basically what I resort to doing is asking colleagues whose computer works to update the library using the same account for me.

Basically on Windows no matter if it's new library or old one, I always get the "Update" prompt, and trying to update the Library doesn't do it, it just immediately gives me back the Update prompt.

It's been going on for years, version and after version, even Windows versions after another 🤣😭 and that issue has never been solved.

I have spent many times hours calling the Adobe customer service about it, they made me do all kinds of things like creating a completely new Windows user account and all these kinds of steps, and they could never find what's wrong nor bring any fix.

So if you face the same issue, I suggest you just give up, XD is just never going to be working for you... 

Well I have read through this issue since KatieH UX first posted. I updated XD(45.0.62.17) recently and since yesterday I am having the same issue! It boggels the brain that it has not been sorted yet.
Can someone help?!

Potential Solution - Here's what worked for me.

After receiving a few responses from Adobe (followed by dead silence), I took matters into my own hands.

As referenced in my earlier responses in this thread (under the name Cubelodyte), I posited that the issue was related to recursion between 2 or more libraries. 

Here was the setup - 

We had 2 libraries: Icons and Major Components.

Many of the major components in the MC library were built with nested icon components from the Icons library. 

Solution: Combine the 2 libraries into one so that no library contains any reference to components in another library.

Other Potential Contributing Factors - Nested Components Shared Between Non-library Project Files

I had been building nested components for years before they became officially supported as "a thing" in XD. I called them compound components (or compound symbols -- that's how long I've been using them). This means that many components that ultimately became library components were being shared from file to file in the Cloud without the governance of the Cloud Library architecture. In fact, many of them were shared between local files before the Cloud rolled in and put a fog over nearly everything I had created over my first 2 years of using XD.

Somewhere around the introduction of  Libraries and the new feature "Nested Components" was the point at which many of my components became delinquent and started causing all manner of disruption in the files that shared them (broken links, components that are no longer used in a document but cannot be deleted or made local, etc.). 

Hypothesis:

Premise - Sharing components between XD project files has never worked completely.

There has always been a function for re-linking broken component links and it has never worked. The introduction of the Cloud and Libraries has probably fixed all of this (As of this week, XD officially prevents any sharing of components except via libraries). I suspect that anyone who begins creating new design systems and new libraries using XD and Adobe Cloud will have no issues. It is only those of us who are carrying forward legacy design project collections that experience the growing pains of system improvements that are not truly backward compatible. 

Therefore - These issues will not present themselves in a fresh, clean design system based on the lastest XD release.

Since I was not willing to toss aside 4 years worth of design work, I tested this hypothesis by bringing all the components of our Icons library into the Main Components library. I used the "Make Local" function to create component instances inside the MC library and then eliminated the Icons library altogether. Since doing so, I have had no further issues with the infinite update.

Note 1:

The solution outlined above is not for the faint of heart. Any project file included direct references to icons in the Icons library had to be manually updated to use icons from the the MC Library. This meant first finding all the broken link components, making them local, and then replacing them with their counterparts in the MC library by dragging from the Assets panel onto the existing instances in the document. 

This process is very time-consuming. For most applications, this would only be necessary if the legacy document is current enough to need updating any time the official component is modified. 

Note 2:

Although the libraries had been in a perpetual state of "you need to update", they were, in fact updating successfully enough that changes were propogating to the project files that used them. 

This is a joke adobe, and it been hapening to me for the past 2 months without a fix, I had to move my team over to Figma as a last resort. Good luck getting this to work.

Hello,

I am having the same issue with the latest update 40.1.22. on Win 10. Already lost a full day in contact with Customer Support and trying different solutions, which didn't help. On top of the bug with the update button, I also got a recovered version of the affected library. It auto generates even if I delete it. At this point in time, our team is stuck and unable to progress on our project.