1

I am working on a school project to create basic android apps. It runs very well before I added few classes (I copy-paste them from my previous classes, it has the same logic/structure but different XML)

When I tried to run my 'updated' app, logCat always show this error:

05-07 09:19:15.402: E/AndroidRuntime(1370): FATAL EXCEPTION: main
05-07 09:19:15.402: E/AndroidRuntime(1370): java.lang.RuntimeException: Unable to instantiate application android.app.Application: java.lang.IllegalStateException: Unable to get package info for com.anatomi; is package not installed?
05-07 09:19:15.402: E/AndroidRuntime(1370):     at android.app.LoadedApk.makeApplication(LoadedApk.java:509)

and then, on the emulator, the "unfortunately, application has stopped" message appears. However after I pressed OK, it's not even crashing and the app runs as normal.

Am I missing something? I'm pretty sure that the .java and .xml have the right structure, and the manifest too.

Onik
  • 19,396
  • 14
  • 68
  • 91
Arya
  • 47
  • 1
  • 1
  • 9
  • Check http://stackoverflow.com/a/10158241/28557 – Vinayak Bevinakatti May 07 '14 at 13:43
  • thanks for your quick response, @Vinayak.B I can see that the error message shows up because I run it on 4.3 emulator **and** with the app still running there. what I'm worried is, will it be causing the same error on the real device? I've deleted the 'new' classes and try to recreate them at the moment. – Arya May 07 '14 at 13:57

1 Answers1

2

This happens sometimes when pushing a new version of your app to the device or emulator, when the old version is swapped with the new version. During that time, the package is not available, and this 'crash' occurs.

This is nothing to worry about, as this scenario will not occur in 'real life' (assuming Play Store updates are handled more gracefully, as I've never seen these crashes there).

nhaarman
  • 98,571
  • 55
  • 246
  • 278