IssueTracker

Info from an internal link that i won't post here:

"AndroidViewModel causes subtle and unavoidable problems in Robolectric tests."

"Robolectric tests create a new Application instance for each test case. AndroidViewModel stashes the application instance in a static field during the execution of the first test case that runs, and retains it across test cases. This causes your test (and any Dagger dependencies) to use an inconsistent application context than your AndroidViewModel instances."

"This issue is easily mitigated. AndroidViewModel is simply a convenience to avoid creating a custom ViewModelProvider.Factory. To workaround this issue, just create a custom factory for your ViewModel."

I think it can be fixed by checking whether the mApplication of sInstance is different to the application passed into getInstance. If so, recreate the instance.