OnDestinationChangedListener won't get called if it navigates somewhere in response to current destination. [190228815]

Fixed

Bug

Status Update

No update yet.

Description

sh...@google.com

created issue #1

Jun 4, 2021 10:40PM

Component used: Navigation Version used: 2.3.5 Devices/Android versions reproduced on: Irrelevant ;)

Repro steps:

In a OnDestinationChangedListener, set things up so that if the new destination is A, nav to B.
Set the current destination to A.
Add the OnDestinationChangedListener to the NavController.

Expected Result: OnDestinationChangedListener receives callback when it is set, and then receives a callback when it causes navigation to B.

Actual Result: OnDestinationChangedListener receives callback when it is set, and then DOES NOT receive a callback when it causes navigation to B.

After the OnDestinationChangedListener is set, this sort of reentrant call works as would be expected, but when getting the callback after having set the OnDestinationChangedListener, it does not.

I think this simply requires swapping

mOnDestinationChangedListeners.add(listener);

and

if (!mBackStack.isEmpty()) {
            NavBackStackEntry backStackEntry = mBackStack.peekLast();
            listener.onDestinationChanged(this, backStackEntry.getDestination(),
                    backStackEntry.getArguments());
        }

in NavController.java. :)

Comments

il...@google.com <il...@google.com> #2Jun 4, 2021 10:57PM

Is there any updates? This is a big problem!

il...@google.com <il...@google.com> Jun 8, 2021 07:26PM

Assigned to il...@google.com.

il...@google.com <il...@google.com> Jun 9, 2021 12:00AM

Accepted by il...@google.com.

ap...@google.com <ap...@google.com> #3Jun 9, 2021 03:05AM

Hi there - could you provide more context on the issue & a sample project to reproduce? Database locked exceptions are quite difficult to pinpoint without a repro project. Thanks!

il...@google.com <il...@google.com> #4Jun 9, 2021 03:42AM

Marked as fixed.

Hi. It is reproduceable on some users by using this code:

suspend fun <R> MyDatabase.workaroundWithTransaction(block: suspend TransactionScope<R>.() -> R) {
    useWriterConnection {
        it.immediateTransaction(block)
    }

    // TODO: Temporally fix https://issuetracker.google.com/issues/340606803#comment2
    // Manually triggers invalidation
    invalidationTracker.refreshAsync()
}

sh...@google.com <sh...@google.com> #5Jun 11, 2021 05:07PM

Maybe it is about this? https://android-review.googlesource.com/c/platform/frameworks/support/+/3114928

I am not sure.

Issue 190228815