Status Update
No update yet.
Comments
ja...@google.com
From the other issue:
note that it is never the right approach to attach a
<deeplink>to an<activity>destination as that will never give you the right behavior when using anon another app's task (where the system back should immediately take the user back to the app that triggered your deep link). Instead, you should attach your deep link directly to your second activity (either by manually writing the appropriate implicit deep link <intent-filter>or by adding the<deeplink>to the start destination of a nav host in that second activity).
A lint error saying as such when a <deepLink> element is added in Navigation XML would go a really long way to avoiding this case. Our navigation-runtime-lint artifact that would contain this check.
tj...@gmail.com
We have some
Description
The Transition Kotlin extensions target the Framework Transition class which is a bit confusing, as most framework classes are being deprecated in favor of their AndroidX counterparts, Fragments for example.
As it stands, the KTX libraries for Transitions cannot be used with androidx.transition.AutoTransition. Does this mean android.transition.Transition should be used over androidx.transition.AutoTransition?
Thanks.