Core Apps » ChatSecure:Android

This bug is still present in 12.4.2. Noticed that all you need to do to reproduce this is to close CS in recent apps. Setting the phone to sleep is not even necessary.

Still present in v12.5.

This bug is not resolved and still present in v12.6.2. Please resolve this bug. Chatsecure should not exit/restart when swiped away in recent apps, but rather continue to work and not crash. This bug is crucial, because many people who use other IM apps are used to the fact that swiping away an IM app keeps the app running.

I've repro'd it once. Here is the crash log I see:

E/AndroidRuntime(21098): FATAL EXCEPTION: main
E/AndroidRuntime(21098): java.lang.RuntimeException: Unable to start activity ComponentInfo{info.guardianproject.otr.app.im/info.guardianproject.otr.app.im.app.NewChatActivity}: java.lang.NullPointerException
E/AndroidRuntime(21098): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2211)
E/AndroidRuntime(21098): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2261)
E/AndroidRuntime(21098): at android.app.ActivityThread.access$600(ActivityThread.java:141)
E/AndroidRuntime(21098): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1256)
E/AndroidRuntime(21098): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(21098): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime(21098): at android.app.ActivityThread.main(ActivityThread.java:5103)
E/AndroidRuntime(21098): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(21098): at java.lang.reflect.Method.invoke(Method.java:525)
E/AndroidRuntime(21098): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:737)
E/AndroidRuntime(21098): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
E/AndroidRuntime(21098): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime(21098): Caused by: java.lang.NullPointerException
E/AndroidRuntime(21098): at info.guardianproject.otr.app.im.app.NewChatActivity$ChatViewPagerAdapter.<init>(NewChatActivity.java:980)
E/AndroidRuntime(21098): at info.guardianproject.otr.app.im.app.NewChatActivity.onCreate(NewChatActivity.java:185)
E/AndroidRuntime(21098): at android.app.Activity.performCreate(Activity.java:5133)
E/AndroidRuntime(21098): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1087)
E/AndroidRuntime(21098): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2175)
E/AndroidRuntime(21098): ... 11 more
W/ActivityManager( 512): Force finishing activity info.guardianproject.otr.app.im/.app.NewChatActivity

Seems related to the fact that app "swiping" on Jellybean actually kills the nbackground service as well:

https://groups.google.com/forum/#!topic/android-developers/LtmA9xbrD5A

This is a potential workaround:
https://code.google.com/p/android/issues/detail?id=53313

Perhaps we should turn this into a feature? Swipe from history could do signout-all and stop the service. This way we will have a predictable behavior and users would know what to expect.

This is not completely resolved. Actually the app restarts when having swiped the app away and after that losing internet connection. After that the app is practically useless and needs to be killed.

I see. That means that the issue is a general one with broadcast receivers, and we have to move the network status broadcast receiver away from the :remote process. Will take care of it ASAP.

Just for clarification. In previous versions the app crashed after swiping away without the need of a signal loss. It is only in the recent version that the app seems to work after you have swiped it away and don't lose your internet connection. To make it crash now you additionaly have to lose your connection.

Applied in changeset chatsecureandroid|commit:d16579e249ee62dd53f97a36da7ea8f4e2e60019.