WAI
Status Update
Comments
mi...@gmail.com <mi...@gmail.com> #2
I notice the same issue and LogCat shows the following message:
Google Play services out of date. Requires 3159100 but found 3136130
Google Play services out of date. Requires 3159100 but found 3136130
ad...@google.com <ad...@google.com>
il...@google.com <il...@google.com> #3
Same here.
"Google Play services out of date. Requires 3159100 but found 3136130"
"Google Play services out of date. Requires 3159100 but found 3136130"
mi...@gmail.com <mi...@gmail.com> #4
me as well....
Google Play services out of date. Requires 3159100 but found 3136130
Google Play services out of date. Requires 3159100 but found 3136130
il...@google.com <il...@google.com> #5
I was hopeful that the release of API 18 (4.3) would have created a solution to this, unfortunately it includes version 3158130
mi...@gmail.com <mi...@gmail.com> #6
Having the same issue:
07-25 00:03:54.998: W/GooglePlayServicesUtil(27293): Google Play services out of date. Requires 3159100 but found 3158130
07-25 00:03:54.998: W/GooglePlayServicesUtil(27293): Google Play services out of date. Requires 3159100 but found 3158130
Description
Currently, they only way to work use a viewmodel with Navhosts and Hilt is with hiltViewModel. However, these instances are only tied to its composable, and is a such destroyed when the composable is no longer visible. As a developer, its usually convenient to keep some state beyond the lifecycle of a compose, but that is currently not possible.
Similarly, using Fragments, we are able to use `by activityViewmodels()` to access an activity scoped viewmodel, but this is not possible with NavHosts.
Use Case:
Access state and values that needs to persist beyond the lifecycle of hiltViewModel, which is currently very short-lived.