NavigationViewTrackingStrategy is not tracking child destinations about dd-sdk-android

[AdamGrzybkowski]

Thanks for the answer

What you could do for now is use the FragmentViewTrackingStrategy, and provide your own ComponentPredicate to only keep specific fragment classes as views.

That's what I did

[xgouchet]

Hi Adam, and thanks for raising this issue. Indeed we only detect automatically the top navController in an activity, for the sake of simplicity. The goal is to detect whenever the "main" screen changes. If a fragment have a children navigation, it'd be complex to automatically know what should actually count as a "screen", as several destinations would be active at the same time, and the RUM product only consider one View to be active at any given time.

Being able to handle such a situation is something we might look into, but it's a non trivial enhancement. We need to know which destinations are "screens" and which are less important changes.

What you could do for now is use the FragmentViewTrackingStrategy, and provide your own ComponentPredicate to only keep specific fragment classes as views.