IssueTracker

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 an implicit deep link on 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 <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 guide to writing Lint checks in AndroidX is a good place to start to start a navigation-runtime-lint artifact that would contain this check.

We have some public docs on writing library lint rules. Specifically the xml lint rule part should be pretty helpful.

CL is WIP: https://android-review.googlesource.com/c/platform/frameworks/support/+/2064176

The following release(s) address this bug.It is possible this bug has only been partially addressed:

• androidx.navigation:navigation-fragment:2.6.0-alpha07

NavBackStackEntry is still not triggering RESUMED on androidx.navigation:navigation-fragment:2.6.0-alpha09 in certain cases, where after a locale or uiMode change with

AppCompatDelegate.setApplicationLocales
AppCompatDelegate.setDefaultNightMode

Issue can be reproduced with attaching LifecycleObserver to the currentBackStackEntry of a Home fragment like so:

       findNavController().currentBackStackEntry?.lifecycle?.let {
            if (it.currentState.isAtLeast(Lifecycle.State.RESUMED)) {
                Timber.d(Constants.LOG_INFO, "lifecycle.currentState", "resumed")
            } else {
                val testLifecycleObserver = object : DefaultLifecycleObserver {
                    override fun onResume(owner: LifecycleOwner) {
                        Timber.d(Constants.LOG_INFO, "lifecycle.currentState", "onResumed")
                        it.removeObserver(this)
                    }
                }
                it.addObserver(testLifecycleObserver)
            }
        }

After performing a config change as mentioned above on a Settings fragment, upon performing a popBackStack/navigateUp to Home fragment, the DefaultLifecycleObserver's onResume will not be triggered. Issue does not occur if a config change is not performed.

I believe this was actually addressed as part of the Navigation 2.6.0-beta01 release. Can you try that out and see if you can still reproduce?