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

Project: platform/frameworks/support
Branch: androidx-master-dev

commit b90079595f33f58fece04026a97faa0d243acdb1
Author: Yuichi Araki <yaraki@google.com>
Date: Wed Sep 18 16:55:49 2019

Change the way to detect mismatch between POJO and query

This fixes cursor mismatch warnings with expandProjection.

Bug: 140759491
Test: QueryMethodProcessorTest
Change-Id: I7659002e5e0d1ef60fc1af2a625c0c36da0664d8

M room/compiler/src/main/kotlin/androidx/room/processor/QueryMethodProcessor.kt
M room/compiler/src/main/kotlin/androidx/room/solver/TypeAdapterStore.kt
M room/compiler/src/main/kotlin/androidx/room/solver/query/result/PojoRowAdapter.kt
M room/compiler/src/test/kotlin/androidx/room/processor/QueryMethodProcessorTest.kt
M room/compiler/src/test/kotlin/androidx/room/testing/TestProcessor.kt

https://android-review.googlesource.com/1123258

https://goto.google.com/android-sha1/b90079595f33f58fece04026a97faa0d243acdb1

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

The following changes were cherrypicked through Coastguard (

https://android-build.googleplex.com/coastguard/)
Release Track: (

https://android-build.googleplex.com/coastguard/dashboard/6093116828680192/#/cherrypickHistory/all)
Created: 2019-10-14 17:23:42.610596+00:00
Changes: aosp/1123258

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

Marked as fixed.

Project: platform/frameworks/support
Branch: androidx-master-dev

commit bdde5a1a970ddc9007b28de4aa29d60ffa588f08
Author: Yigit Boyar <yboyar@google.com>
Date: Thu Apr 16 16:47:05 2020

Re-factor how errors are dismissed when query is re-written

This CL changes how we handle errors/warnings if query is
re-written.
There was a bug in expandProjection where we would report warnings
for things that Room already fixes automatically (

b/140759491

).
The solution to that problem (I7659002e5e0d1ef60fc1af2a625c0c36da0664d8)
solved it by deferring validating of columns until after re-write
decision is made. Unfortunately, this required changing PojoRowAdapter
to have a dummy mapping until it is validating, make it hard to use
as it does have a non-null mapping which is not useful.

This CL partially reverts that change and instead rely on the log
deferring logic we have in Context. This way, we don't need to break
the stability of PojoRowAdapter while still having the ability to
drop warnings that room fixes. This will also play nicer when we
have different query re-writing options that can use more information
about the query results.

Bug: 153387066
Bug: 140759491
Test: existing tests pass
Change-Id: I2ec967c763d33d7a3ff02c1a13c6953b460d1e5f

M room/compiler/src/main/kotlin/androidx/room/log/RLog.kt
M room/compiler/src/main/kotlin/androidx/room/processor/QueryMethodProcessor.kt
M room/compiler/src/main/kotlin/androidx/room/solver/TypeAdapterStore.kt
M room/compiler/src/main/kotlin/androidx/room/solver/query/result/PojoRowAdapter.kt

https://android-review.googlesource.com/1288456

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

Ah, thanks for fixing this Ian!

I meant to let you know that I will look into the other strategies you suggested. In case you are still interested, we show an identity verification screen given various conditions so we may navigate to it (and then back to where the user was previous to us navigating to it) often. One place where we check to see if it is needed is in an OnDestinationChanged callback. Also in that callback we do some other stuff like some analytics tracking and some other ui decoration stuff for certain screens. Given the current behavior we had to do some special stuff, but with your bug fix our code can be simplified!

Thanks so much!

Issue 190228815