java.lang.RuntimeException: Unable to instantiate application android.app.Application: java.lang.NullPointerException at LoadedApk.makeApplication [duplicate]

Answer 1

This is an error from the .project file in your project. You can open other .project files on a project without errors for comparison. Almost, you can see wrong with <buildCommand> tag in this file.

Answer 2

I also get this error when running my app on 4.x or above both emulator and actual device, but the error does not prevent my app to be launched, so I simply ignore it.

Answer 3

Looked into the ICS source code - It seems like for whatever reason the Package Manager can't get your package info - it could just be an eclipse/ADT bug where eclipse holds some kind of lock on the file, but whatever it is, it doesn't seem like something that you could cause with your code. I would suggest running a clean, uninstalling the app from the emulator/device, or if those don't work, you might try a fresh eclipse workspace.

Another thing that might be an issue is if you're using a Library project - try unlinking the two, cleaning, and then linking them back up again - but thats it for my bag o' tricks :)

UPDATE: yorkw gives a better explanation for why this occurs and its resolution here: RuntimeException: Unable to instantiate application

Answer 4

This is (unsurprisingly*) a bug in Eclipse/ADT/adb. I managed to fix it by uninstalling my app from the emulator. Hopefully it won't come back, but I'm not going to hold my breath.

*Seriously, Eclipse & ADT seem to be the buggiest pieces of software I've ever used. In only one day I've run into at least four different very annoying bugs! (This one, ddms broken pipe, workspace in use but it isn't, dex out of memory.) It's embarrassingly shoddy. Thank god we have stackoverflow!

Edit: I spoke too soon. The bug returns as soon as you run the app a second time.

Answer 5

I struggled with this error too.The error occurs inconsistently. Found out it was a library dependency that was not included in the build path for API level 16 (android-support-v4)

Answer 6

It also happens if you're trying to call new Intent(getActivity(), ActivityXY.class) when activity was finished and garabage collected. It's usually an indicator that you forgot to cancel some asynchronous operations when the activity/fragment was destroyed