We have a brand new look! Take a tour with us and explore the latest updates on Adobe Support Community.
There are main components in my document that come up with a red link ikon, even though its located in the same document. Why?
<Title renamed by moderator>
Sorry to hear you're experiencing issue with linked component in XD. We would like to confirm if this is the main file with main component in which you're getting red error.
We will try our best to investigate the issue and help you.
Hi, I am working on XD with a number of main components, but as soon as I did the last update of the program, they started to break. When I need to edit a main component and I change between its states, the green rhombus (indicating that it is a main component) changes to a red link icon (as if the component came from another file, and as if it were broken link). I need to know what is going on because the file I am working on defines the design system of other files as it is a large project.
I am attaching two images of the same component. This text field was a main component, but as soon as it went to a state 2 that defined an action for me, it changed to another type of broken link component.
Please, I need a quick answer, because as I told you, it is a big project and it can affect my work flow.
Thanks a lot!
We are sorry for the trouble. We would like to confirm if this is the similar issue as mentioned here: https://community.adobe.com/t5/adobe-xd/unlinked-error-on-main-component-in-main-document-in-xd/td-p...
If so, we would request you to please share the asked details and we will try our best to investigate the issue.
Yes, it is a similar problem, main components created in that file, which later became components with the red link icon. In fact, they sometimes become just copy components. I don't know if it's a bug in the program.
Additionally, I work this file in the cloud with other partners and the same thing happened to them.
Their versions are:
Thanks for sharing the requested information. Is it possible for you to share the file with me over a private message so that I can check at my end and investigate more about it? If yes, please upload the file to a shared location such as CC or Dropbox and share the URL with me over a PM.
I will try my best to help.
No - I have tried to make the compontents local and then save the update the library. As I know the the other files are linked to this file I was guessing I could make them local without loosing the links. It worked ok, but then when I close the document, the links are back to red again when I reopen it.
I am sorry I can't share the file as it is confidential material.
Thanks for getting back. In order to investigate further, we would need these details-
If you're unable to provide them due to confidentiality, we would request you to please connect with us directly using our Contact us page and initiate a chat with us so that we can file a feedback ticket for you.
We'll try our best to help.
How is this possible? The main component comes up with a missing link? Its no supposed to be linked to anything at all - as it is a MAIN component created in this document.
I have the most updated version of XD.
I don't know who in my organisation I am supposed to contact about this - can yu help me if I share the file with you privately?
Thanks for reaching out. Yes we would need the below files to investigate the issue-
Please upload the files to a shared location such as Dropbox and share the URL with me over a PM.
We will try our best to help.
For your Source document that was used to create your Library, have you ever used Save As... to create a copy of that document?
It's ok to do that to make a backup copy.
But it causes problems if you use that copy to start another Library. The issue is that the components in the copied document keep the same internal IDs of the original doc, so if you Publish that to another Library, there will be Components with duplicate IDs. Documents that use the component may refer a a different Library than you are expecting. This could explain what you have described here.
Use this method to create a new Library based on an existing Library:
Open source document of existing Library in XD, select all Components on canvas that you want in new Library, and then Copy. Create a new cloud doc named what you want to call your new Library, then Paste. All of the Components should be Linked to the existing document. For each Linked Component in Assets Panel, right-click > Make Local (which generates new internal ids). You should be able to multi-select a few at a time to save time. Finally, Publish new Library.
Hope this helps,
I have a similar issue. Yesterday, I was updating my Master document getting it ready to publish as a library by making sure there were no links to other libraries in it and that all my components are local. (I followed the guidance here: https://helpx.adobe.com/xd/help/migrate-design-systems-to-creative-cloud-libraries.html) Yesterday when I finished work at around 7pm, I had only a few more links (no more than five) to convert to local. This morning, when I started work, brand new components I created in this document as assets and many of the other LOCAL assets (I stopped counting at 30!) are now showing with a red link next to them saying that the Element is missing from the library. This file has never been published as a library but has links from an existing published library that this one was copied from. I suspect that is part of the problem.
I've just had a look at your Contact us page (and looked in lots of other places) and nowhere on that page does it have a phone number, an email address or a chat function. I'm essentially left with no way to contact you. Like others on this thread, I can't upload a file here because it's confidential.
How do I proceed? How can I fix this problem?
Also, the ones I created yesterday that are showing with red links only give me "Highlight on canvas" when I right-click on them. I don't get the option to make them local — probably because they're already local since I created them yesterday and for some reason the thing thinks their associated with a library they were never a part of to begin with. Very confusing and frustrating! They all say "Element is missing", but some can be made local and some can't! Makes no sense!
Sorry to hear that you are having problems. I think the reason that some Components can be made Local and others cannot is because some are nested inside other Linked Components. Convert all of the ones that you can to Local then go back and check the others to see if they now provide Make Local command.
Hope this helps,
Hello, I was making local all the components that appeared to me with a broken link, I closed the file, but when I reopened it, the components that I had fixed were damaged again.
Seriously, this must be a big bug in the tool that you guys should fix soon.
Yes, we are aware of that problem, but we're still trying to track down all workflows that cause it. Can you answer a couple questions?
1. For your Source document that was used to create your Library, have you ever used Save As... to create a copy of that document? It's ok to do that to make a backup copy. But it causes problems if you use that copy to start another Library -- could this have been done to create your Library?
2. Do you copy Components in one document and then paste in another document? We suspect this is one of the main causes of this problem, so we recommend that Components are dragged from Libraries instead.
Thank you for reporting the issue. It is bit confusing that how master component turned into broken linked component.
Could you please provide clear details or short clip of Published document with its all assets and explain in more brief.
Having this issue also, its a major concern.
For me the components are inexplicably breaking in the master library document in which the component has been created. It's causing chaos.
I am having the same issue. But my local components say they're linked to one of my libraries they haven't been anywhere near.
We have highlighted this issue to our Product team and they are investigating on the workflow. We will get back to you if they need information from your end.
The best you can help us with is to share a video of your workflow showing the behavior so that they can try replicating their end and check the root cause of the issue.
It's happening on a lot of documents now, so it is hard to isolate. Including one of my libraries. I'm coping components to a blank document breaking then copying back. I'm doing this becasue XD doesn't let you duplicate a master. You don't let us organize components within a library. Libraries are slow and require constant updating.
Who thought it was a good idea to break everyones workflow. For a program that does UX/UI design, Adobe may want to think about doing some user research before breaking everything.