I'm sorry in advance to be harsh, but I'm tired of trying to figure out why things just don't work as expected. Seriously Adobe, the XD components system doesn't work and, more important, is full of bugs.
Please check out the attached as one of the many examples of things which don't work with the component system. This file contains 2 artboards:
Check out this right artboard, right click its Android slave component and select "Reset to master". Something suddently appears which is not in the master component.
I spend countless hours on such problems in the component system. This is really a mess and almost unusable in the professionnal environment. Sorry Adobe.
Funny bug: this site refuses to attach a xd file. What a symbol! This file is here: https://www.dropbox.com/s/lei39174i9xxk9r/this-is-bad.xd?dl=0
Sorry for the delay in response and thank you for sharing the file. I have downloaded the file at my end on my windows machine. I did click on reset to master but I didn't see anything. Could you please share a video where it shows the issue after resetting to master?
I will try my best to help.
Here is a short video.
In short: when I reset to master state, 2 icons appears on the right, which are NOT in any state of the master component.
And this is just one single example of all the problems of the XD components system. I've many many more.
I know the same problem - your master component on the artboard is not showing correctly - just delete it from an artboard and then select "edit master" from right clicking on it in the library panel. You'll see your master actually has those two icons - just remove them after these actions and they will be gone from all instances. This happens for me regularly if I keep master components on the artboard. Hope this workaround helps you (to properly work in Adobe XD you have to know all sorts of workarounds and "known issues").
I totally agree. I have used Sketch, Figma, and Xd and 80% of my workflow is based on complex components; however, Xd's component system is extremely unreliable.
1 - When creating nested components, sometimes the master works ok, but all of its copy will have duplicates of components or other layers inside that component
2 - There were cases where the component and its copies were working perfectly, then a few days later they were all broken even without touching them
3 - Responsive resize literally gives me headaches. When hiding a layer, it will rescale the component as it should; however, the component bounding box will still be the same size as if the element was not hidden. What pisses me off is that if I keep hitting "hide"/"show" at times the bounding box WILL resize the way it's supposed to. Here's an example: https://drive.google.com/file/d/1EpZC63tgbBQvijzHG4a5dQoolbMKb-2F/view?usp=sharing
You can clearly see the bounding box is not consistent (on both master and the copy) and that's a very basic component.
It also annoys me that I can't save shadows as styles.
It can work with a basic component system, but start adding complexity and other components and you have a recipe for a nightmare.
The way it stands now, I find Xd's components unstable and unreliable, I can't have it on my library and risk having my team messing up our UI because things are not resizing as they should.
I have never had such stress when trying to figure out components in other platforms, but boy oh boy, Xd really made me rage quit several times. I'm honestly considering redesigning the whole project in another program as I can't deal with the Xd component issues anymore.
And don't even get me started on the library ><
And I'm on the latest version (188.8.131.52) as of the time of posting, with the added 3D transform. Too bad I'm hating Xd so much that the new feature though interesting doesn't even excite me as I wanna run away from Xd.