Project

General

Profile

Bug #1567

massive number of crashes on startServerConnectionDetection

Added by cpg over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
-
Target version:
-
Start date:
10/28/2014
Due date:
% Done:

0%


Description

We have 112 crashes in this startServerConnectionDetection method! We need to fix this.
(somehow reviews are great!)

Do we have a a guess as to why does this happen??
Is it possible that it's because the user does not have a local server?

java.lang.NullPointerException
       at org.amahi.anywhere.server.client.ServerClient.startServerConnectionDetection(ServerClient.java:113)
       at org.amahi.anywhere.server.client.ServerClient.connectAuto(ServerClient.java:171)
       at org.amahi.anywhere.fragment.NavigationFragment.setUpServerConnection(NavigationFragment.java:342)
       at org.amahi.anywhere.fragment.NavigationFragment.setUpServerConnection(NavigationFragment.java:327)
       at org.amahi.anywhere.fragment.NavigationFragment.onItemSelected(NavigationFragment.java:322)
       at android.widget.AdapterView.fireOnSelected(AdapterView.java:892)
       at android.widget.AdapterView.access$200(AdapterView.java:49)
       at android.widget.AdapterView$SelectionNotifier.run(AdapterView.java:860)
       at android.os.Handler.handleCallback(Handler.java:730)
       at android.os.Handler.dispatchMessage(Handler.java:92)
       at android.os.Looper.loop(Looper.java:213)
       at android.app.ActivityThread.main(ActivityThread.java:5225)
       at java.lang.reflect.Method.invokeNative(Method.java)
       at java.lang.reflect.Method.invoke(Method.java:525)
       at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:741)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:557)
       at dalvik.system.NativeStart.main(NativeStart.java)

History

#1 Updated by megabitdragon over 6 years ago

  • Status changed from New to Feedback
  • Assignee set to cpg

This issue was the main reason for the 1.1.0 release. I checked the Crashalytics dashboard and I don't see it happening in the new version. Do you have information from other sources? If not I would say this should be solved. BTW, there were almost 160 crashes and about 80 users affected.

#2 Updated by cpg over 6 years ago

  • Status changed from Feedback to Closed
  • Assignee changed from cpg to megabitdragon

Also available in: Atom