Participant

Answered

Unlinked error on main component in main document in XD 42.1 version

Forum|Forum|4 years ago
July 28, 2021
10 replies
7695 views

There are main components in my document that come up with a red link ikon, even though its located in the same document. Why?

Product performance

This topic has been closed for replies.

Correct answer Randy Edmunds 2

A fix was released in v44.1. Please upgrade to this release and let us know your results.

Thanks,

Randy

Randy Edmunds 2Correct answer

Adobe Employee

A fix was released in v44.1. Please upgrade to this release and let us know your results.

Thanks,

Randy

S

Soundar5C12

Participant

I also face the same issue

-

-x-x-x-x-x-x-x-

Participant

Exact same issue over here. I noticed it yesterday even though I only updated to the latest build today. After the update, it's much worse. Some components can be made local and some can't. I don't even have the option to delete some of these.

My master component library is now insisting that all of my components can't be used because they're not local to the file. But I built everything in this file from scratch. I just finished making new components yesterday, updated to the latest XD version today (44.0.12.7), and this morning all of those components are broken. This is a show stopper. I've been using XD from the very beginning but I never experienced this level of broken-ness with an update before.

Cocoshoou

Participating Frequently

I installed CC and XD yesterday and this morning I created components in a doc, published them and used them in an other doc. I closed for break and when I opened again the components had a red link. I can't even locate them.

I contacted the support and while chating I created new components. At some point he told me to shut XD, sign off/on of CC to make them work again. Worst, the new one I was created also had a red link. Nothing is resolved.

Rishabh_Tiwari

Legend

Hi there,

Sorry to hear about the trouble. Please DM the file and other details asked on the post and I will escalate this further. To send the DM, please click on my name.

Regards

Rishabh

T

TL Price

Known Participant

I can tell you right now it's caused from copying components from one document to another to break them and move them back. And I had to do this because Adobe XD forgot to add a DUPLICATE MAIN COMPONENT feature. Because again, they don't bother to talk to the people who are using it.

The migrating shared components to libraries shouldn't have happened before the core components issues were addressed:

1. merging duplicates components
2. duplicating main components (not creating instances)
3. merging instant changes with main component for all the million times a designer changed an instance and not a master.
4. arranging component layers.

These need to be Adobe XD's priorities. I waited a year being nice, and waiting. These are core issues, and now my design systems are broken and my workflow has tripled.

T

TL Price

Known Participant

Does Adobe have an ETA on when this will be fixed?

Randy Edmunds 2

Adobe Employee

There is a change coming in v44 that should fix case for Components that show Link to same doc/library.

But, we're still try to reproduce some other cases. Please let us know if you have a reproducible recipe for getting into this situation when creating a new Library. Thanks in advance.

Regards,

Randy

T

TL Price

Known Participant

I don't create new libraries all the time. That isn't remotely how I work. Adobe's libraries are buggy and take time to sync, cause load issues, and multiple components, because you don't have a simple MERGE function. I have a central design system I built into a couple libraries. If I'm going to rebuild this library, it's in Figma. I understand that Adobe's core user are people pretending to be UI designers, but you also need to think about the people who need this for production work. Right now, I'm recommending my team and every designer I know to move away from this poorly implemented program.

Do better.

Also you're last updated added groups, but those groups didn't translate when moving components from a library. Utterly useless. Thanks.

T

TL Price

Known Participant

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.

Harshika Verma

Community Manager

Hi All,

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.

Thanks,

Harshika

T

TL Price

Known Participant

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.

D

Dylan5E38

Participant

Having this issue also, its a major concern.

D

Dylan5E38

Participant

For me the components are inexplicably breaking in the master library document in which the component has been created. It's causing chaos.

Harshika Verma

Community Manager

Hi there,

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.

What happen when you hover to the red error, does it show any error message?
Please share the version of XD and the OS of your machine.
Does that happen with this specific file?

We will try our best to investigate the issue and help you.

Thanks,

Harshika

P

Pablo5C5C

Participant

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!

Harshika Verma

Community Manager

Hi Pablo,

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/12310919

If so, we would request you to please share the asked details and we will try our best to investigate the issue.

Thanks,

Harshika

Randy Edmunds 2

Adobe Employee

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,

Randy

D

danielabh

Participant

Hi, can you please help me with a problem I have today? Suddenly (I think after updating the library) a few components that are master components of a cloud document got misconfigured and they now appear in the components panel with a linked icon in red saying that the library is missing, when they are master components of that opened document.

Thanks

A

Ansubedi03

Community Manager

Hello,

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.

Regards,

Anita Subedi

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.