Participant

Answered

[Design] -Components not updating properly

Forum|Forum|6 years ago
June 12, 2019
5 replies
12369 views

Hello,

I am struggling with a possible bug of components not updating properly to match master component. I had to do some some rework on my master components, where I deleted some features and added in new. My master component looks just as it should, however when I place the component from the asset list, it now has has all the new features, but also the old ones, like they would've never been removed at all..!?

Here's an example, the one on the left is the master component, as you can see from the selection box. The one on the right is the same component placed from the assets list. It has two plus sign overlapping, the old one I have removed from the master component, and the new updated sign.

I've tried everything to "refresh" the asset list but I just can't make it work. This is happening with many of the components simultaneously. I think the only way is to remove the component completely and then creating it again. However this is quite a big effort since I have to replace all of the instances and relink all the links in the prototype...

Any advice?

{Renamed By MOD}

This topic has been closed for replies.

Correct answer SwapnilShrivastava

Hi,

Thanks a lot for sending the file and video capture.

I am glad that you are able to resolve your first problem by removing out of sync master and regenerating master element. That was a smart workaround.

Regarding your second problem, unfortunately that's a limitation with nested components. If you have a nested component which is not master then any change done to it will be considered as override (even if it is in master). We have a story in backlog to workout a solution for this limitation. But for now you have to live with it.

In you case you can just ungroup nested component and automatically that change will be propagated to all other instances of tab bar. Here is the quick view of the behavior (nested symbol - YouTube )

Thanks again for sending such a detailed description/video and source file.

M

mowglivj

Inspiring

This whole situation begs belief. The issue here is that the component implementation is ill-conceived to say the least. I keep having to manually update component instances which makes the use of components pointless.

If overrides are aloud, how come there are no signifiers for this?? It all quickly becomes a mess and it doesn't take much thinking to realise that that would be the case. Just the fact that changing a button label involves changing the label in every single state tells you everything you need to know about how unfit for purpose the whole thing is.

J

joenapp19

Participating Frequently

I HAVE TO SAY ...I've been very excited about Adobe XD and have my team of 75 people using it (moving away from InVision) but this issue is giving me major pause. The power behind having a component library/design ssystem comes down to this feature/bug. How can you have a design system if components do not update. Adobe I think you know my company and this issue is defintely making us re-consider our move to XD.

I

iOnRails

Participant

Please fix this issue, is unbearable to work with. There should be a way to remove components from a nested component group with non of these issues. Thanks 😞

J

johnc67583066

Participant

We are having the same issue. We did an update to an input component and all our mockup files across our platform are now jacked up. We spent the day going into every component used and reset to master, then added our local changes. We made one more change to the design system master file and when designers updated their design files that are using the design system, all the inputs jacked up again. Parts of the components were positioned off the artboard and multiple layers of text were stacked on top of one another.

B

bfouillet

Participant

Did you find a solution ? Still struggling with this update bug. I have more than 500 components with constraints / states for each states... it is a nightmare

C

clemensg96250075

Known Participant

This problem still exists in 27 and Adobe does not seem to get things work more than half a year later – I have provided files and detailed reports and still no solution to these kind of problems. If things don’t get better with the next version I’ll return to Sketch. I don’t get paid for testing Adobe’s software.

V

vincero

Participant

This problem still isn't fixed (or entirely fixed) and Adobe people should definitely get on that. Components is among the top 3 most important parts of Adobe XD. You simply can't build a UI well using Adobe XD without using components and this bug is so central to the component feature! I've run into it several times and it has set me back, at this point, hours. I'm not going to use Adobe XD for UI/UX design again until this is fixed, but I'm too far in with this project, so I'll have to deal with it for now. Honestly, otherwise this app works really well. Suggestion for Adobe people: stop focusing on building new features until this is fixed - it's that annoying and unintuitive to circumvent.

V

vincero

Participant

My bug is that I have a working master component and I cannot duplicate it in any way and get a working second version.

jessicama.ads

Known Participant

I'm having the same issue, I don't have any nesting. It just doesn't work. I have a side nav bar and for the life of me the EDIT master list doesn't work at all. There is no way to push the overrides. It's just supposed to work.

Video capture:

https://we.tl/t-4g94R4aRci

S

SwapnilShrivastava

Participating Frequently

jessicama.ads Looking at the video capture, I am guessing you have done some structural overrides to the instance (probably extra grouping or changing parent of that icon in the instance) and hence it has gone out of sync with master.

If above theory is correct, then you can make it work by following steps:

1. select that instance (and others that are affected), right click "Reset to Master"

2. Perform above operation of changing things in master.

Or alternatively you can directly use "Reset to Master" on instance in your existing instance. It will remove any override on the instance and force sync to master.

Please let me know if above suggestion does not work.

jessicama.ads

Known Participant

Hi

Thing is I don't have a "reset to master" on the instances. I have the most updated XD software.

I ended up going the long route and copy pasting a new set on every single artbooard.

Why don't I have this option? That would have saved me a lot of time before and should be there.

S

SwapnilShrivastava

Participating Frequently

Thanks for reaching out to us Niklas.

From your description it looks like your master component and underlying definition of component in asset panel got out of sync. We can surely help you, though we would need more information to debug and see how you got into this state. Here are things that will help us debug:

1. XD file : source file where you see this issue. I recommend to save as a local file, delete all the other stuff and just keep above component. You can either share a dropbox link or any other file sharing.

2. If you can recall all the steps which you performed on master which got you into this state. For example, does it involve resetting inner components or grouping things inside master etc.

Looking forward to hearing from you.

Niklas DruggeAuthor

Participant

Hi,

I actually managed to get workaround for my initial problem by deleting the master component that was placed on an artboard and then placing it again from the list with the "Edit master component" command. This then made a new version of the master component that had the unwanted overlapping features, and by removing them from this master component, it started to work normally. Still I think it's not supposed to work like that, but anyways - got it to work.

However, I encountered another similar kind of a problem related to master component not updating properly, and I wasn't able to make it work even with the solution I described above. From the link you'll find the XD file in question, and also a very brief screen cap video I made to better demonstrate the issue.

To describe it briefly: I have a "tab bar" component, which consists of two tab components. I want to make the other tab dimmed by making an override on that element inside the tab bar component. Everything's fine in the master tab bar component, but when I place an instance of the tab bar from the asset list, it has lost the override.

Link to Xd file & video:

WeTransfer

S

SwapnilShrivastavaCorrect answer

Participating Frequently

Hi,

Thanks a lot for sending the file and video capture.

I am glad that you are able to resolve your first problem by removing out of sync master and regenerating master element. That was a smart workaround.

Regarding your second problem, unfortunately that's a limitation with nested components. If you have a nested component which is not master then any change done to it will be considered as override (even if it is in master). We have a story in backlog to workout a solution for this limitation. But for now you have to live with it.

In you case you can just ungroup nested component and automatically that change will be propagated to all other instances of tab bar. Here is the quick view of the behavior (nested symbol - YouTube )

Thanks again for sending such a detailed description/video and source file.

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.

Scanning file for viruses.

This file cannot be downloaded