Status Update
No update yet.
Comments
il...@google.com
ap...@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.
Description
Component used: SavedState
Version used: 1.1.0
When
SavedStateRegistryis asked toperformSave, itputBundleThis means that in cases like Fragments, where the Fragment itself has a
SavedStateRegistryand the fragment's view has its ownSavedStateRegistry, the overall saved state is increased doubly so (at what seems like a cost of 0.2KB per fragment).While not a significant part of the total saved state, this can add up with deep stacks.