android-lifecycle | A diagram of the Android Activity / Fragment lifecycle | Android library

The solution still in beta for the saved state said by Google. The only solution, for now, to persist the data is using Room.

To answer your questions:

1. Data in ViewModel is only persisted throughout the lifecycle of your activity. So if your app dies, your data is not saved. If you want it to persist, consider integrating an off-line data persistence library like Room or you can also use SharedPreferences depending on your use case.

2. According to this post: Android LiveData - how to reuse the same ViewModel on different activities?

When you call ViewModelProviders.of(this), you actually create/retain a ViewModelStore which is bound to this, so different Activities have different ViewModelStore and each ViewModelStore creates a different instance of a ViewModel using a given factory, so you can not have the same instance of a ViewModel in different ViewModelStores

In other words, different activities cannot share a single ViewModel. So if you want to switch pages while retaining data in your ViewModel, consider using fragments inside your activity instead.

Here is some things to try rebuilding after each. Let me know how it goes.

Try clicking on Tools menu -> Kotlin -> Configure Kotlin in Project.

Try clicking on Tools menu -> Kotlin -> Configure Kotlin Plugin Updates

Try adding

Update the classpath 'com.google.gms:google-services:4.1.0' in project build.gradle.

There is an abstract onResume() method in the CordovaPlugin class which you can override like this:

The correct answer is SingleObserver, this is perfect for networking.

Your ChronometerViewModel (being a child of ViewModel) does not get destroyed with the orientation change of the Activity.

ViewModel is a class that is responsible for preparing and managing the data for an Activity or a Fragment. It also handles the communication of the Activity / Fragment with the rest of the application (e.g. calling the business logic classes).

A ViewModel is always created in association with a scope (an fragment or an activity) and will be retained as long as the scope is alive. E.g. if it is an Activity, until it is finished.

In other words, this means that a ViewModel will not be destroyed if its owner is destroyed for a configuration change (e.g. rotation). The new instance of the owner will just re-connected to the existing ViewModel.

I suggest you read the documentation of ViewModel: https://developer.android.com/reference/android/arch/lifecycle/ViewModel.html

I think that your best (long term) option is to have a setup along with the integration of the library (i.e. pass the Application in an entry point of your library).

That said, there is an undocumented way to get the current Application. as described here: https://stackoverflow.com/a/12495865/458365