In my custom component property name is "experienceFragmentPath"

Above post talks about JCR resolver, as DAM path was different. My issue is different. I have same DAM path.

It shows me all the assets and content policies of my page but does not show the assets of XF which i have used in my custom component

No, this issue is not there in OOTB/Core XF component. I am facing this issue with my custom component.

I have a customer component, which take experience fragment(XF) as input through dialog box. When i try to publish the page which has custom component, it gives me option to publish XF used in a component but does not give me option is publish the assets associated with the XF. Due to this assets in...