Hello, we're a big company in Spain using XD and I must say it's been an error until now.
- Libraries do not mantain the states in a master component, only the default view
- People need to have total access to the master XD document to have really functional components across teams, huge problem. If they copy an instance of a component from another document, and I update the master of the style guide, they don't see the changes reflected, because only the children are updated, not the grandchildren.
Please, solve the continuous synchronization problems when coworking, it is impossible to list them all.
<The Title was renamed by moderator>
We understand it could be frustrating for you. If I heard you right, it looks you're also experiencing the similar issue mentioned here: https://adobexd.uservoice.com/forums/353010-adobe-xd-bugs-read-only/suggestions/37647550-master-comp... If so, please submit your feedback and check Joe comment under comment section.
Let us know if that helps.
No, it doesn't help because the solution is still a problem.
We can't make a design system with this tool. Nested components inside components do not work well and neither copy an instance of a master component in a new project.
The team is aware of these issues and is in the process of fixing them. From what I know, there have been improvements to this experience in the latest version. Just in case you have not updated to the latest version, can you try updating and let us know if you continue to face these issues?
Copy link to clipboard
Let's try to get a bit more precise about these problems.
In order to understand what you're trying to achieve, it's crucial to do the impossible: to list those problems, and see if there are unnecessary misunderstandings about certain features.
Your title mentions "co-editing", but your description of the issue doesn't seem to have something to do with co-editing (working together at the same time, in the same file). Is that correct ?
Adobe CC Libraries and Adobe XD are no good friends (yet), to state it mildly.
And I can imagine you're having problems with it, while finding solutions for the other problem with Components.
But about these Components: you mean by "children" the (perhaps altered) instances of the original Component in File A, and with "grandchildren" the copied and therefore linked (and perhaps altered) components in File B ? And if the link can't be established from File B back to File A (because users simply don't have access to File A), any change in A will not be passed through to B ? Well, that's expected behavior...
Hope this helps ?