IssueTracker

since these are in public API (:/) we need to do this in 1.2

Opening diff shortly

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

commit d576cbdc911cba16638a44fd8223391a90a07ef7
Author: Mike Nakhimovich <digitalbuddha@users.noreply.github.com>
Date:   Tue Aug 11 09:30:34 2020

    [GH] Hide deprecated internal API.
   
    ## Proposed Changes
   
    * `RoomDatabase.java` has protected `mCallbacks` field which is leaking in the API docs, we should @Hide it.
   
    ## Testing
   
    Test: Ran unit tests locally
   
    ## Issues Fixed
   
    Fixes: 76109329
   
    This is an imported pull request from https://github.com/androidx/androidx/pull/61.
   
    Resolves #61
    Github-Pr-Head-Sha: 6440daa3a63752c7f9d5ba2a390248cd85bc634f
    GitOrigin-RevId: fe92d8466a59b44b218b6ca3cbd57dcda17992f7
   
    Change-Id: Id599cdf5b02b32bdae0166266fb7da967598fe92

A       room/runtime/api/current.ignore
M       room/runtime/api/current.txt
M       room/runtime/api/public_plus_experimental_current.txt
M       room/runtime/api/restricted_current.txt
M       room/runtime/src/main/java/androidx/room/RoomDatabase.java

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

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

commit a57c661958456fc4782121ec37858fd767d5d2f2
Author: jbwoods <jbwoods@google.com>
Date:   Mon Mar 25 17:29:53 2019

    Class ViewModelLazy class to take a ViewModelStoreProducer
   
    Changed ViewModelLazy to take a ViewModelStoreProducer instead of a
    ViewModelStoreOwner making the class more generic.
   
    Test: ran FragmentViewModelLazy, ActivityViewModelLazy, and
    ViewModelProvider test.
    ./gradle checkApi
    BUG: 111614463
    Change-Id: I111b4df94cd6c8b272a2fec89a66de86616aa1ad

M       activity/ktx/src/main/java/androidx/activity/ActivityViewModelLazy.kt
M       fragment/ktx/api/1.1.0-alpha06.txt
M       fragment/ktx/api/current.txt
M       fragment/ktx/src/main/java/androidx/fragment/app/FragmentViewModelLazy.kt
M       lifecycle/viewmodel/ktx/api/2.1.0-alpha04.txt
M       lifecycle/viewmodel/ktx/api/current.txt
M       lifecycle/viewmodel/ktx/src/main/java/androidx/lifecycle/ViewModelProvider.kt
M       lifecycle/viewmodel/ktx/src/test/java/androidx/lifecycle/ViewModelLazyTest.kt

https://android-review.googlesource.com/932932
https://goto.google.com/android-sha1/a57c661958456fc4782121ec37858fd767d5d2f2

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

commit 1e09fdb1e5ce72359698bf5fa37e31a931e8c575
Author: jbwoods <jbwoods@google.com>
Date:   Mon Mar 25 22:36:00 2019

    Add ViewModel support at NavGraph scope
   
    Allows users to get a ViewModelStore for a NavGraph. The ViewModelStore
    is retrieved using the graph ID. Only NavGraphs on the NavController
    back stack can create a ViewModelStore.
   
    Test: New Tests and reran NavControllerTest
        ./gradlew checkApi
    BUG: 111614463
    Change-Id: Ib60bb0eda2c1dc9d2cd5a5aa132162105d172b68

M       navigation/common/src/main/java/androidx/navigation/NavBackStackEntry.java
M       navigation/fragment/ktx/api/2.1.0-alpha02.txt
M       navigation/fragment/ktx/api/current.txt
M       navigation/fragment/ktx/build.gradle
A       navigation/fragment/ktx/src/androidTest/java/androidx/navigation/fragment/NavGraphViewModelLazyTest.kt
A       navigation/fragment/ktx/src/main/java/androidx/navigation/NavGraphViewModelLazy.kt
M       navigation/fragment/src/main/java/androidx/navigation/fragment/NavHostFragment.java
M       navigation/runtime/api/2.1.0-alpha02.txt
M       navigation/runtime/api/current.txt
M       navigation/runtime/build.gradle
M       navigation/runtime/src/androidTest/java/androidx/navigation/NavControllerTest.kt
A       navigation/runtime/src/androidTest/java/androidx/navigation/NavControllerViewModelTest.kt
M       navigation/runtime/src/main/java/androidx/navigation/NavController.java
A       navigation/runtime/src/main/java/androidx/navigation/NavControllerViewModel.java

https://android-review.googlesource.com/932046
https://goto.google.com/android-sha1/1e09fdb1e5ce72359698bf5fa37e31a931e8c575

Navigation 2.1.0-alpha02 now supports ViewModels at the navigation graph level.

This allows you to write such as:

val viewModel: RegistrationViewModel
    by navGraphViewModels(R.id.registration_graph) { factory }

or if you're using Java:

ViewModelStore store =
    navController.getViewModelStore(R.id.registration_graph);
RegistrationViewModel viewModel = new ViewModelProvider(store, factory);

And the ViewModel will live until the containing host and its ViewModelStore is cleared or the navigation graph is popped off the back stack.

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

commit 3cc9b77742508c095f3268b60956967bce46f0ed
Author: Ian Lake <ilake@google.com>
Date:   Sat Mar 30 08:40:04 2019

    Save and restore back stack UUIDs for getViewModelStore()
   
    As each NavBackStackEntry has a UUID which matches
    the non-config ViewModelStore for each graph, we
    need to make sure that those UUIDs are properly
    saved and restored across configuration changes to
    ensure that when you ask for a particular
    ViewModelStore, you get the same object back.
   
    Test: new testSaveRestoreGetViewModelStore
    BUG: 111614463
    Change-Id: Ie174eeae7318e9b8ba233e58df57f960a8861d99

M       navigation/common/src/main/java/androidx/navigation/NavBackStackEntry.java
M       navigation/runtime/src/androidTest/java/androidx/navigation/NavControllerTest.kt
M       navigation/runtime/src/main/java/androidx/navigation/NavController.java

https://android-review.googlesource.com/936699
https://goto.google.com/android-sha1/3cc9b77742508c095f3268b60956967bce46f0ed

unresolved reference: by navGraphViewModels(R.id...)?

In that case what if I have a global navigation action screen let's say for this example a CountryPickerFragment where I want to share data between this screen and the parent caller fragment only (not the entire navigation graph) and I want it cleared after the parent is done how could I scope  the ViewModel in that case?

That is a different issue, that is not yet available. What you want is actually opening a screen while waiting for a result. Check:

https://issuetracker.google.com/issues/79672220

What's the difference between graph scoped and parent Fragment/Activity scoped ViewModel?
Navigation graph use child fragment manager to navigate its graph, I think it equals to use parent Fragment scoped ViewModel.

In reference to #8 how would this work when one needs to implement an app flow of "single activity wih multiple fragments" where also you could share a parent fragment viewmodel with it's child/nested fragments. Referring to your talk on Google IO/19 navGraphViewModels work with only the fragments within the same graph, so how does one share the parent fragment viewmodel with it's child fragment in such a case?