IssueTracker

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

  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
 

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

Project: platform/frameworks/support
Branch: androidx-main

commit ce0a07e52f9bbc60ff0983101da22d782ddff391
Author: Jeremy Woods <jbwoods@google.com>
Date:   Tue Aug 10 17:42:26 2021

    Ensure we keep track of all transitioning entries
   
    We currently keep up with all transitioning entries in a set, which
    means we can't keep up with multiple entries that are considered "equal"
    but actually are different objects.
   
    This currently breaks navigate with popUpTo and transitions since we
    will pop first, causing us to consider the old entry as transitioning,
    then when we navigate we attempt to add the new entry as transitioning,
    but since it is "equal" to the old one, the set just ignores the add.
   
    We need to instead make transitionsInProgress a List, meaning we can
    have multiple entries that "equal" each other. This also means we need
    to be sure to clear all the "equal" entries from the list whenever one
    of them is complete.
   
    Relnote: "Re-selecting the same tab when using navigation compose with
    multiple back stacks will no longer result in a blank screen."
   
    Test: added testSameEntry
    Bug: 194925622
   
    Change-Id: I860dc9f2cc2516924c03dba491a37aa8ace99bb3

M       navigation/navigation-common/api/current.txt
M       navigation/navigation-common/api/public_plus_experimental_current.txt
M       navigation/navigation-common/api/restricted_current.txt
M       navigation/navigation-common/src/main/java/androidx/navigation/NavigatorState.kt
M       navigation/navigation-testing/src/androidTest/java/androidx/navigation/testing/TestNavigatorStateTest.kt
M       navigation/navigation-testing/src/main/java/androidx/navigation/testing/TestNavigatorState.kt

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

This is really weird but I believe this issue resurfaced in 2.7.1. I was using 2.5.3 and it was working just fine but today i updated the dependency and this started happening.

Same for me. I was using 2.7.1. When I selected the arrow to navigate back twice quickly, the app would go back one screen, then the screen would go completely blank. When I reverted to 2.5.3, that issue went away.

Same for me. I was using 2.7.2 and, oh man, when I encountered this issue I didn't even know where to start debugging. Thank god it worked just fine when I downgraded to 2.5.3.

same here, just updated from 2.5.3 to 2.7.3 and screen is blank when navigating for second time on same screen

To reproduce this issue, I attached a basic navigation project that consists of screens with buttons that go from one Screen to another.

Additionally, I attached two videos. One using Navigation 2.6.0 shows it is working fine, while the other video using Navigation 2.7.1 shows the strange behavior of a blank flash.

I tested all 2.7.x versions and the 2.8.0 alpha, and it's still happening.

Additionally, in some cases, the transition of the screens is that it enters from the upper right corner to the lower left. This behavior is bizarre and erratic since there is no defined animation, and it happens randomly on the screen. Only when many buttons on the screens are pressed quickly.

Feel free to tag me if there is any advance :(. (I am new here, IDK how this works)

#15 you should report this in a new ticket

Here is a solution that works for me. The blank screen seems to happen if there's no screen in the previous history to navigate to when a user double-clicks the back arrow too quickly.

if (navController.previousBackStackEntry != null) {
                        navController.popBackStack()
                    }

And here is my solution for bottom navigation, always check if the current route is not equal to the route being navigated to:

onClick = {
                    if (selectedItemIndex != index) {
                        localNavController.navigate(
                            route = item.route,
                            builder = {
                                launchSingleTop = true
                                restoreState = true
                                popUpTo(localNavController.graph.startDestinationId) {
                                    saveState = true
                                }
                            }
                        )
                    }
                }