83

I am trying to write a sample app using Android architecture components and but even after trying for days I could not get it to work. It gives me the above exception.

Lifecycle owner:-

public class MainActivity extends LifecycleActivity {

    public void onCreate(Bundle savedInstanceState)
    {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.activity_main);
        TextView textView = findViewById(R.id.tv_user);
        PostViewModel viewModel = ViewModelProviders.of(this).get(PostViewModel.class);
        viewModel.loadPosts();
        viewModel.getPost().observe(this, new Observer<Post>() {
            @Override
            public void onChanged(@Nullable Post post) {
                if(post != null) {
                    textView.setText(post.toString());
                }
            }
        });
    }
}

ViewModel:-

public class PostViewModel extends ViewModel {
    private MediatorLiveData<Post> post;
    private PostRepository postRepo;

    PostViewModel() {
        post = new MediatorLiveData<>();
        postRepo = new PostRepository();
    }

    public LiveData<Post> loadPosts() {
        post.addSource(postRepo.getPost(),
                post -> this.post.setValue(post)
        );
        return post;
    }

    @NonNull
    public LiveData<Post> getPost() {
        return post;
    }
}
Parag Kadam
  • 2,659
  • 4
  • 18
  • 39

28 Answers28

136

Make your constructor public.

CommonsWare
  • 910,778
  • 176
  • 2,215
  • 2,253
  • 5
    Such a minor mistake but such big impact. Thanks. – Parag Kadam Jul 09 '17 at 15:36
  • However strangely Android studio gives a warning after making constructor public saying "Access can be package-private" . – Parag Kadam Jul 09 '17 at 15:52
  • 4
    @ParagKadam: Android Studio does not know that the lifecycle components need the constructor to be public. Android Studio only goes by what it can see through explicit code references. – CommonsWare Jul 09 '17 at 16:05
  • 27
    Still getting the error in a fragment, both class and constructor are already public. – ahmadalibaloch Jan 19 '18 at 09:49
  • 5
    My constructor is public, but I received this error: Caused by java.lang.RuntimeException: Cannot create an instance of class com.randa.android.model.search.SearchActivityViewModel at android.arch.lifecycle.ViewModelProvider$NewInstanceFactory.create(ViewModelProvider.java:153) at android.arch.lifecycle.ViewModelProvider$AndroidViewModelFactory.create(ViewModelProvider.java:210) at android.arch.lifecycle.ViewModelProvider.get(ViewModelProvider.java:134) at android.arch.lifecycle.ViewModelProvider.get(ViewModelProvider.java:102) at com.randa.android. – MrVasilev Sep 14 '18 at 10:18
  • 2
    Funny thing is it works in debug mode but crashes when the app is compiled in release mode. – b4da Jan 14 '19 at 18:45
  • 1
    Both constructor and the class need to be public ! – Marco Mar 05 '20 at 17:40
  • 1
    *And* the class must be static if it's a nested class in your Activity. – Edward Falk Aug 06 '20 at 02:11
  • This is such annoying bug, which I failed to find a good solution for almost a month. – Ab Morphious Aug 18 '20 at 15:22
56

if you are using Hilt, ensure your activity/fragment is having @AndroidEntryPoint annotation

You Qi
  • 5,401
  • 7
  • 42
  • 54
  • This does not provide an answer to the question. To critique or request clarification from an author, leave a comment below their post. - [From Review](/review/low-quality-posts/26963524) – Andrii Omelchenko Aug 18 '20 at 18:56
  • well @AndriiOmelchenko, have you tried Hilt with injection in viewModel constructor? because I believe this is an honest mistake that most developers will make that will cause `Cannot create an instance of class ViewModel` crash during run-time. – You Qi Aug 19 '20 at 01:53
  • 7
    I'm using Dagger Hilt, and that answer saved me a lot of time, thanks! – Canberk Ozcelik Nov 30 '20 at 13:20
  • I always make the same mistake and find myself here. Thank you. – UmutTekin Jan 05 '21 at 09:06
  • same here. I always always make the same mistake. wondering around then always find the answer here – user1865027 Mar 16 '21 at 23:05
  • This was an answer for me too. I wonder why some are so quick to give negative unhelpful views if they don;t have knowledge of a domain. On another note, Fragments were working at some point without the `@AndroidEntryPoint`. The viewmodel jammed when i made it a little more complicated, with an injected argument in the constructor. – nyxee Apr 05 '21 at 14:42
  • Even after putting @AndroidEntryPoin I'm getting java.lang.RuntimeException: Cannot create an instance of class ViewModel – Samsad CV May 20 '21 at 11:27
19

Make sure your ViewModel has constructor with only one parameter i.e. Application.

example:

public YourViewModel(Application application) {
    super(application);
    ...
vivek
  • 830
  • 7
  • 14
18

If you are using Kotlin make sure to replace any annotationProcessor in build.gradle with kapt.

Like:

annotationProcessor "android.arch.persistence.room:compiler:$rootProject.roomVersion"

Will become

kapt "android.arch.persistence.room:compiler:$rootProject.roomVersion"

and add

apply plugin: 'kotlin-kapt' on top of the buidl.gradle file.

Annotation Processing with Kotlin

Max
  • 12,408
  • 4
  • 48
  • 62
  • 2
    It fixed my problem. It may not be the right answer for java, but it is correct for "Cannot create an instance of class ViewModel in Kotlin" – Eoghan Oct 31 '18 at 22:52
  • 1
    @Eoghan I posted the answer for the exact same reason because it took me quite a while to understand this issue. But ppl are not gentle and keep downvoting lol even though I have clearly mentioned if you are using kotlin. – Max Nov 01 '18 at 02:07
  • It saved me, i hate this android logger, i got an exception about something and the reason is actually something else – Milos Oct 30 '19 at 17:48
  • @Milos maybe you should use "log filters" in Android Studio. – Ab Morphious Aug 18 '20 at 15:24
12

I had this problem following google's roomdb CodeLab. Solution was changing the following.

Edited

Add the following Build dependencies to Gradle file (as of 2/22/2020)

implementation 'androidx.fragment:fragment:1.2.2'
implementation 'androidx.lifecycle:lifecycle-process:2.2.0'
implementation 'androidx.lifecycle:lifecycle-service:2.2.0'
implementation 'androidx.lifecycle:lifecycle-viewmodel-savedstate:2.2.0'
annotationProcessor 'androidx.lifecycle:lifecycle-compiler:2.2.0'

Imports within the fragment

import androidx.lifecycle.ViewModelProvider;
import androidx.fragment.app.Fragment;
import androidx.lifecycle.Observer;

Creating the viewModel. Add one of the following methods.

Note: I'v seen this done many ways. I believe the correct way is using getDefaultViewModelProviderFactory(). But I have been using requireActivity().

 new ViewModelProvider(requireActivity(),getDefaultViewModelProviderFactory()).get(YourViewModel.class);

|

 new ViewModelProvider(requireActivity()).get(YourViewModel.class);

          

ViewModelProvider Docs

Deprecated

implementation 'androidx.lifecycle:lifecycle-extensions:2.2.0-rc01'
annotationProcessor 'androidx.lifecycle:lifecycle-compiler:2.2.0-rc01'
this.mitch
  • 437
  • 5
  • 10
  • 2
    The latest android lifecycle documentation says that the lifecycle-extensions dependency is now deprecated https://developer.android.com/jetpack/androidx/releases/lifecycle# However, if I remove that dependency from the gradle file I am getting the cannot create an instance of class viewmodel error when I start my app. I tried adding all of the other dependencies listed as current, even the optional ones, but it won't work without the lifecycle-extensions dependency. For now, I have to keep the deprecated dependency. I am still trying to find why it fails without this dependency. – Howard Feb 23 '20 at 17:44
  • Good info @Howard , I updated my answer based on your comment. – this.mitch Feb 25 '20 at 00:32
  • Thanks for this answer, I had the same issue following roomdb CodeLab, the only thing I had to add was implementation 'androidx.fragment:fragment:1.2.5' – Rck Nov 28 '20 at 18:06
9

There are few reason to throw the exception . I have mention some of them..

  1. Make sure your view Model class is public

  2. Make sure your view model class constructor is public

  3. Make sure you have added the dependency in your gradle file for lifecycle also if you use room and other libraries you have added ..

  4. if you create object any other dependent class in your view model class constructor . Other class can throw error to create the instance of viewModel

Ali Zarei
  • 2,349
  • 3
  • 21
  • 37
Hoque MD Zahidul
  • 5,772
  • 2
  • 26
  • 34
  • 2
    Great for the 4th point!!! It really solves me after finding your step by step solution. – Vji May 08 '19 at 12:33
6

It was not completely obvious to me, but when getting this error I resolved it by creating a public constructor. My constructor was derived from the Android Developer examples and contained the Repository as a parameter. Creating an additional constructor that was empty with no params and having it public solved the issue.

i.e., in your case

public PostViewModel() {}

Brandon
  • 1,300
  • 1
  • 15
  • 24
6

Make the class and constructor public it solved my problem .

RaghavPai
  • 564
  • 7
  • 12
6

DggerHilt can also be the reason, If you are using it make sure your activity/fragment is having @AndroidEntryPoint annotation on it.

Rahul
  • 2,374
  • 2
  • 22
  • 36
4

If you used viewmodel inside your activity check that your activity extends "DaggerAppCompatActivity" or not

For instance

public class UserComments extends AppCompatActivity 

change this to

public class UserComments extends DaggerAppCompatActivity
3
  1. Mostly, Solution is making Class and Constructor Public as the other answers
  2. It may also be a runtime error, check the Logcat Error Logs if there are multiple causes listed.
lomec
  • 1,289
  • 1
  • 11
  • 9
3

Extend AndroidViewModel from your ViewModel class.

public class YourViewModel extends AndroidViewModel {

    public YourViewModel(Application application) {
        super(application);

        //Todo: ...
    }

}
Zeero0
  • 1,887
  • 17
  • 34
3

In my case, the reason was that I was trying to get a shared instance of the ViewModel in my fragment too soon - before the activity was created. What happens when the application is restoring its state after being killed.

Preconditions:

  1. My ViewModel has a public constructor.
  2. My ViewModel has multiple arguments. But this is absolutely fine as I use ViewModelFactory to construct the ViewModel.
  3. My Fragment and Activity shares the same instance of the ViewModel. In other words: Activity creates the ViewModel and the fragment receives the same instance later.

Code in activity:

override fun onCreate(savedInstanceState: Bundle?) {
    super.onCreate(savedInstanceState)

    //factory is constructed using Dagger
    val factory = App.get().components().appComponent.getMapViewModelFactory() 
    //activity creates the instance of MapViewModel
    viewModel = ViewModelProviders.of(this, factory)[MapViewModel::class.java]
}

Code in fragment:

override fun onCreate(savedInstanceState: Bundle?) {
    super.onCreate(savedInstanceState)

    //fragment receives the instance of MapViewModel
    viewModel = ViewModelProviders.of(activity!!)[MapViewModel::class.java]
    ...
}

When I open the app for the first time, everything works fine: activity creates an instance of ViewModel; I open Fragment, which gets the instance of ViewModel. But when the application is trying to restore its state after being killed, first it calls the body of onCreate of the Fragment and then the body of onCreate of the Activity. At that point, the fragment can't get the ViewModel as Activity had not created it yet.

Solution 1: Move the code when the fragment gets the ViewModel from onCreate to onViewCreated. This is fine as I observe all live data in onViewCreated as well.

override fun onViewCreated(view: View, savedInstanceState: Bundle?) {
    super.onViewCreated(view, savedInstanceState)

    viewModel = activity?.run { ViewModelProviders.of(this)[MapViewModel::class.java] } ?: throw Exception("Invalid Activity")

    viewModel.getSurveyDateLiveData().observe(viewLifecycleOwner, Observer<String> { dateTextView.text = it })
    ...
}

Solution 2: Create the instance of ViewModel in Activity.onCreate before super.onCreate is called. In this case, you can get the ViewModel in your fragment's onCreate.

override fun onCreate(savedInstanceState: Bundle?) {
    
    val factory = App.get().components().appComponent.getMapViewModelFactory()
    viewModel = ViewModelProviders.of(this, factory)[MapViewModel::class.java]
    
    super.onCreate(savedInstanceState)
    Timber.d("cc: onCreate: $this ")
}

Solution 3:

If you are injecting repository instance in your ViewModel, Check that you are not using @Inject constructor(...): ViewModel() to inject your repository, but rather **@ViewModelInject constructor(...): ViewModel()**

Rahul
  • 2,374
  • 2
  • 22
  • 36
Andrew
  • 960
  • 9
  • 22
3

If you are using Hilt then don't forget to add these four dependencies.

    implementation "com.google.dagger:hilt-android:2.28-alpha"
    kapt "com.google.dagger:hilt-android-compiler:2.28-alpha"
    implementation 'androidx.hilt:hilt-lifecycle-viewmodel:1.0.0-alpha01'
    kapt "androidx.hilt:hilt-compiler:1.0.0-alpha01"

Note:- If any of these dependencies are missing you will get Cannot create an instance of class ViewModel error

iamkdblue
  • 2,545
  • 1
  • 21
  • 35
2

I got this after migrating to AndroidX.

There's a bug in androidx.lifecycle:lifecycle-viewmodel:2.0.0-beta01 where Proguard removes the constructor.

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

Fix by upgrading to 2.0.0, and remember to update your proguard rules if needed.

My error message looked like this:

java.lang.RuntimeException: Cannot create an instance of class my.custom.viewmodel.CustomViewModel
at androidx.lifecycle.ViewModelProvider$AndroidViewModelFactory.create(ViewModelProvider.java:202)
at androidx.lifecycle.ViewModelProvider.get(ViewModelProvider.java:135)
at androidx.lifecycle.ViewModelProvider.get(ViewModelProvider.java:103)
......
Caused by: java.lang.NoSuchMethodException: <init> [class android.app.Application]
at java.lang.Class.getConstructor0(Class.java:2204)
at java.lang.Class.getConstructor(Class.java:1683)
at androidx.lifecycle.ViewModelProvider$AndroidViewModelFactory.create(ViewModelProvider.java:200)
... 34 more


  androidx.test.espresso.PerformException: Error performing 'single click - At Coordinates: 539, 1167 and precision: 16, 16' on view 'with id: my.test:id/button_return_to_main_menu'.
at androidx.test.espresso.PerformException$Builder.build(PerformException.java:82)
at androidx.test.espresso.base.DefaultFailureHandler.getUserFriendlyError(DefaultFailureHandler.java:79)
.....
Caused by: java.lang.RuntimeException: Unable to start activity ComponentInfo{my.custom.domain.MainActivity}: java.lang.RuntimeException: Cannot create an instance of class my.custom.viewmodel.CustomViewModel
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2646)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2707)
Lydia Ralph
  • 1,325
  • 1
  • 18
  • 29
2

if your PostViewModel class is an inner class, make sure its public and static

Lasitha Lakmal
  • 326
  • 1
  • 13
2

For people using Jetpack Compose, Navigation and Hilt

Make sure to use the hiltNavGraphViewModel instead of viewModel.

This is provided by androidx.hilt:hilt-navigation-compose dependency.

More details in the docs.

Duncan Luk
  • 6,326
  • 6
  • 35
  • 58
1

In my case I needed to use a ListItemViewModelFactory to pass in a parameter to my view model.

Loren
  • 728
  • 1
  • 10
  • 15
  • Yes. We have to create `YourViewModelFactory(private val param: String) : ViewModelProvider.Factory` to have a parameter inside `ViewModel`. – CoolMind Mar 30 '21 at 17:35
1

In my case, it was gradle a dependencies problem.

If you are using Livedata,,

build.gradle(Module.app)

not

implementation 'android.arch.lifecycle:extensions:1.1.1'
kapt 'android.arch.lifecycle:common-java8:1.1.1'

use these

implementation 'androidx.lifecycle:lifecycle-extensions:2.2.0'
kapt 'androidx.lifecycle:lifecycle-common-java8:2.2.0'
J.Dragon
  • 450
  • 4
  • 10
1

Please add below code. It worked for me

val binding = FragmentLayoutBinding.inflate(inflater, container, false)

val viewModel = ViewModelProvider(
            requireActivity(),
            defaultViewModelProviderFactory
            ).get(MainViewModel::class.java)
Evgeniy Mishustin
  • 2,858
  • 2
  • 31
  • 68
sharma_kunal
  • 2,018
  • 1
  • 26
  • 27
1

If you're using Hilt Dependency Injection, You probably have missed @ViewModelInject. Because, Hilt provide its own injection for viewmodel.

In my case, I used and @Inject due to this caught into the error.

Sohail Pathan
  • 83
  • 1
  • 5
  • If you face this issue in Kotlin Dagger Hilt even after adding annotations HiltViewModel and Inject, make sure you have updated all hilt dependencies. – Abdul Mateen May 05 '21 at 07:28
0

My problem was that the IDE had added a "abstract" modifier to my ViewModel class.

DBragion
  • 3,561
  • 2
  • 13
  • 11
0

Make ViewModal class and constructure public

John Ruban Singh
  • 1,088
  • 11
  • 15
0

If constructor of your viewmodel is public and accepts only application then make sure you can create your own model without ViewModelProvider. Error message might be much more clear:

val model = YouViewModel(app)
eleven
  • 6,464
  • 2
  • 28
  • 45
0

I'm a proficient Android developer and I have used ViewModel 100s of times with no issue. Today I came across this issue. Spent hours and scrolled through various SO posts. Didn't get solved.

Then I saw that the package name in which I have the ViewModel contains new. Like this:

com.myapp.myfeature.new.feature

I changed new to neww for testing like this: com.myapp.myfeature.neww.feature

and it worked! I hope someone find it useful.

Paras Sidhu
  • 574
  • 1
  • 9
  • 28
  • Good that it worked for you, however this has not got anything to do with ViewModels, you just can't use a keyword in the package name. – Parag Kadam Dec 03 '20 at 12:07
  • Yes Parag but there was no warning and error didn’t point to it. It was only random event to discover that the issue was with Package name – Paras Sidhu Dec 03 '20 at 12:09
  • You could have discovered this issue while working with anything else apart from ViewModels and just because you discovered this issue while implementing ViewModels doesn't make it a valid answer to the question asked above. – Parag Kadam Dec 03 '20 at 12:13
0

If you are using version 2.33-beta and upper remove these dependencies;

implementation "androidx.hilt:hilt-lifecycle-viewmodel:1.0.0-alpha03"
kapt "androidx.hilt:hilt-compiler:1.0.0-beta01"

Keep only these two dependency

implementation "com.google.dagger:hilt-android:2.33-beta"
kapt "com.google.dagger:hilt-android-compiler:2.33-beta"
Ahmet
  • 266
  • 3
  • 9
0

If you face this issue in Kotlin Dagger Hilt even after @HiltViewModel and using @Inject, make sure you have updated all hilt dependencies.

Abdul Mateen
  • 574
  • 7
  • 16
-1

I'm using this example android-arcuitecture-component BasicSample to make a new project, facing a similar error log, found I did'n change de applicatio name

AndroidManifest.xml

and that was my error, to fix put the aplicacion name to de BasicApp, this class is implement in the example.

...
<application
    android:name=".BasicApp"
    android:allowBackup="false"