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 f88d94e1063eab5d615586fa118bf96652bb57a6
Author: Jeremy Woods <jbwoods@google.com>
Date:   Tue Oct 26 15:37:35 2021

    Fix NavBackStackEntry initial Lifecycle state
   
    NavBackStackEntry currently relies on its host lifecycle owner to
    determine the initial host lifecycle state of the entry. This can cause
    issues cause the host state might not reflect the dispatched state, so
    we can end up with a scenario where the entry moves to a state before
    the NavController's lifecycleObserver has dispatched that state.
   
    We should instead make NavBackStackEntries host lifecycle state rely
    directly on NavController's lifecycleObserver's dispatched state. This
    sure that the entries lifecycle is always properly in sync.
   
    RelNote: "NavBackStackEntries will not longer be pushed down to
    `Lifecycle.State.CREATED` after moving to `Lifecycle.State.STARTED` when
    the `NavHost` is added directly to the activity's `setContent()`."
    Test: NavHostTest
    Bug: 203536683
   
    Change-Id: Ia5ac1c2c7e83f90780dd85187519c08debaa6eca

M       navigation/navigation-runtime/src/androidTest/java/androidx/navigation/NavBackStackEntryTest.kt
M       navigation/navigation-runtime/src/main/java/androidx/navigation/NavController.kt
M       navigation/navigation-testing/src/main/java/androidx/navigation/testing/TestNavigatorState.kt
M       navigation/navigation-compose/src/androidTest/java/androidx/navigation/compose/NavHostTest.kt
M       navigation/navigation-runtime/src/main/java/androidx/navigation/NavBackStackEntryState.kt
M       navigation/navigation-common/src/main/java/androidx/navigation/NavBackStackEntry.kt

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

Great news! Thanks a lot for such a quick resolution of this bug, looking forward to next release :)