java.lang.RuntimeException: Unable to instantiate activity ComponentInfo/ ClassNotFoundException

Question

I\'m develop android application and than i wanna additional new Activity i had error on my logcat

My LogCat:

04-19 12:59:17.654: D/AndroidRuntime(18         


        

Answer 1

I agree with what @codercat has advised you to do, but this error also comes when you are using v7 and also v13 in the same project structure for different functionalities. Therefore, i advice you to copy the v13 jar file into the libs folder (DO NOT import it as an external jar) and then check the android libraries and android dependencies. Refresh you project and then clean your project. I am sure the error you are facing will go away.

Answer 2

Cleaning the project worked for me. You might ask me what led to the issue? LOL I tried to upgrade a project to android 5 from 4.4 and then changed my mind and tried to restore it back to kitkat, then voila! this error came up.

Answer 3

Dude, this also happened to me when my app was already published in the marketplace. It was a total disaster. I realized it after 5 hours of already publishing it.

There was no problem by running it with the ADT. Problem was with the generated APK. So if you publish an app, test the installation of the pure APK in your test phone.

As you, I also think that problem was with the the update of my ADT, in my case v22.

The solution was to clean and build the project:

Android java.lang.RuntimeException: Unable to instantiate activity ComponentInfo

Answer 4

you might have declared String a = edt.getText().toString(); or int 5/3 hence such errors use to come

so,
declare them in onCreate method error will resolved

Answer 5

i also having same problem and i just turn off build automatically and build my android project manually and cleaned my project that solved this error for me

Answer 6

When upgrading, the 'Order and Export' of the new 'Android Private Libraries' is not always checked. And the android-support-v4.jar is now in this 'Android Private Libraries' section.

To fix this, go to 'Order and Export' and check 'Android Private Libraries'. Then refresh/clean/rebuild.

After you done this 'fix' for a library project, you may need to just close and re-open any depending project, because they may not see this 'fix' immediately.