Crash after successfully installing app (v0.76)

Crash on adding / deleting application. After the app is successfully added / deleed, f-droid crashes and logcat shows:

E/AndroidRuntime( 4285): FATAL EXCEPTION: main
E/AndroidRuntime( 4285): Process: org.fdroid.fdroid, PID: 4285
E/AndroidRuntime( 4285): java.lang.RuntimeException: Unable to resume activity {org.fdroid.fdroid/org.fdroid.fdroid.AppDetails}: java.lang.RuntimeException: Failure delivering result ResultInfo{who=null, request=1, result=-1, data=Intent { (has extras) }} to activity {org.fdroid.fdroid/org.fdroid.fdroid.AppDetails}: java.lang.NullPointerException
E/AndroidRuntime( 4285): 	at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2812)
E/AndroidRuntime( 4285): 	at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:2841)
E/AndroidRuntime( 4285): 	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2276)
E/AndroidRuntime( 4285): 	at android.app.ActivityThread.access$800(ActivityThread.java:144)
E/AndroidRuntime( 4285): 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1205)
E/AndroidRuntime( 4285): 	at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 4285): 	at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 4285): 	at android.app.ActivityThread.main(ActivityThread.java:5146)
E/AndroidRuntime( 4285): 	at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 4285): 	at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime( 4285): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:732)
E/AndroidRuntime( 4285): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:566)
E/AndroidRuntime( 4285): 	at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 4285): Caused by: java.lang.RuntimeException: Failure delivering result ResultInfo{who=null, request=1, result=-1, data=Intent { (has extras) }} to activity {org.fdroid.fdroid/org.fdroid.fdroid.AppDetails}: java.lang.NullPointerException
E/AndroidRuntime( 4285): 	at android.app.ActivityThread.deliverResults(ActivityThread.java:3389)
E/AndroidRuntime( 4285): 	at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2799)
E/AndroidRuntime( 4285): 	... 12 more
E/AndroidRuntime( 4285): Caused by: java.lang.NullPointerException
E/AndroidRuntime( 4285): 	at org.fdroid.fdroid.AppDetails$4$1.run(AppDetails.java:907)
E/AndroidRuntime( 4285): 	at android.app.Activity.runOnUiThread(Activity.java:4713)
E/AndroidRuntime( 4285): 	at org.fdroid.fdroid.AppDetails$4.onSuccess(AppDetails.java:899)
E/AndroidRuntime( 4285): 	at org.fdroid.fdroid.installer.DefaultInstallerSdk14.handleOnActivityResult(DefaultInstallerSdk14.java:119)
E/AndroidRuntime( 4285): 	at org.fdroid.fdroid.AppDetails.onActivityResult(AppDetails.java:1067)
E/AndroidRuntime( 4285): 	at android.app.Activity.dispatchActivityResult(Activity.java:5423)
E/AndroidRuntime( 4285): 	at android.app.ActivityThread.deliverResults(ActivityThread.java:3385)
E/AndroidRuntime( 4285): 	... 13 more

Thanks for the bug report and the attached logcat. Do you recall whether you had closed F-Droid or at least the App Details screen during the installation? Looks to me like an issue that might be related to that. Also, just in case we can't reproduce on our own devices, could you also let us know what version of Android you are running? Cheers.

It happens just after the app is installed, when I think the display is switching back to f-droid. Also relevant: (1) I run cyanogenmod nightlies, and this started a few weeks ago. (I'm on CM-11-20141203 at the moment). Secondly, "Settings" has also crashed when uninstalling an app, which may be the same bug?

I recently installed fdroid and at the first run when it was refreshing repository, it crashed and stoped working. I had this problem on two lg phone with android 4.4.2. Whenever i try to run fdroid, after some seconds it stop.

I have the same issue on my phone with both F-Droid versions 0.76 and 0.77-test (2014-12-10). My phone is the Samsung Galaxy Gio running CyanogenMod 10.1.

A repeating problem on this phone is the small RAM. Therefore, android kills activities more often (due to low memory) than on other phones. Unfortunately, many developers forget to save the whole state of the activity in the corresponding life-cycle methods. Hence, if android re-creates a terminated activity, not all variables are in the correct state -- NullPointerExceptions are the consequence. I've observed this also with other apps.

I think you should look in the activity code and check your depencies to variables that are not saved in the acitivities instance state.

mentioned in merge request !58 (merged)

Status changed to closed by commit 47e065442edc108d4bb38f9daaa7cdb3fff26b49

mentioned in issue #837 (closed)