Hi,
The problem with this is they have to keep uninstalling and re
installing the app over and over.
I reproduced this error by force remvoing my sdcard with out
unmounting it. This left all the apps on my sd card in the app draw
but with blank icons.
java.lang.RuntimeException: Unable to instantiate activity
ComponentInfo{com.mycompany.app/com.mycompany.app.MAINACTIVITY}:
java.lang.ClassNotFoundException: com.mycompany.app.MAINACTIVITY in
loader dalvik.system.PathClassLoader[/mnt/asec/com.mycompany.app-1/
pkg.apk]
at
android.app.ActivityThread.performLaunchActivity(ActivityThread.java:
2585)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:
2679)
at android.app.ActivityThread.access$2300(ActivityThread.java:125)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:
2033)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:4627)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:521)
at com.android.internal.os.ZygoteInit
$MethodAndArgsCaller.run(ZygoteInit.java:876)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:634)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.ClassNotFoundException:
com.mycompany.app.MAINACTIVITY in loader
dalvik.system.PathClassLoader[/mnt/asec/com.mycompany.app-1/pkg.apk]
at dalvik.system.PathClassLoader.findClass(PathClassLoader.java:243)
at java.lang.ClassLoader.loadClass(ClassLoader.java:573)
at java.lang.ClassLoader.loadClass(ClassLoader.java:532)
at android.app.Instrumentation.newActivity(Instrumentation.java:1021)
at
android.app.ActivityThread.performLaunchActivity(ActivityThread.java:
2577)
... 11 more
the game worked fine last night now it just forces closed.
Everytime I want to use this app I have to uninstall and reinstall and
start over.
On Jan 6, 11:28 am, Emanuel Moecklin <[email protected]> wrote:
> Hi there
>
> I was finally able to "reproduce" the problem on one of my phones.
> It threw the exact same exception I'm normally getting as a market
> crash report. The result of my investigation: no app problem but a
> problem during installation.
> Basically the apk was corrupt and therefore the main activity class
> could not be found. This explanation makes sense because the app
> hasn't even been started yet when the exception occurs so how could it
> be the app's fault? Especially considering the fact that the exact
> same app/apk works fine on many identical devices out there. I'm
> thinking that whatever piece of code installs the apk must be blamed
> for this issue. A fresh installation of the app fixes the issue for
> the user.
>
> Emanuel Moecklin
> 1gravity LLC
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
