RemoteServiceException Error

Question

I have a lot of abnormal arrests, but I not understand how this is possible, because don't understand the origin of the problem. This is the log of abnormal arrest:

android.app.RemoteServiceException:
android.app.ActivityThread$H.handleMessage (ActivityThread.java:1881) at android.os.Handler.dispatchMessage (Handler.java:105)
android.os.Looper.loop (Looper.java:164)
android.app.ActivityThread.main (ActivityThread.java:6938)
java.lang.reflect.Method.invoke (Native Method)
com.android.internal.os.Zygote$MethodAndArgsCaller.run (Zygote.java:327) at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1374)

Other information is that the problem is more showed on devices with Android:7 or more..

Thanks in advance

Answer 1

Im not sure if my problem is the exact same problem as this one. I started getting crash reports on google play just like this. For example

android.app.RemoteServiceException: 
  at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1881)
  at android.os.Handler.dispatchMessage (Handler.java:105)
  at android.os.Looper.loop (Looper.java:164)
  at android.app.ActivityThread.main (ActivityThread.java:6938)
  at java.lang.reflect.Method.invoke (Native Method)
  at com.android.internal.os.Zygote$MethodAndArgsCaller.run (Zygote.java:327)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1374)

I started seeing this around build 189 and did not see this error before 185

So this github checkin still did not have it

And this github checkin had the bug for sure

I was did make some changes related to a foreground service so I am suspecting my issue relates to

Issue Tracker: Context.startForegroundService() did not then call Service.startForeground

Context.startForegroundService() did not then call Service.startForeground()

---- EDIT ----

My issue did turn out to be that I was calling startForegroundService which was not needed because my app was not in the background when it did this.

For sure the issue has been resolved by this commit

Answer 2

There is insufficient information to diagnose this properly.

However, this is an "internal" exception that gets thrown when the looper attempts to handle a "SCHEDULE_CRASH" message. I think that happens when another activity calls ActivityThread.ApplicationThread.scheduleCrash ... but this is not at all clear from the Android source code.

I am guessing that this a result some native application "bailing out". There is typically an app specific message to go with the exception, but it seems to be missing in your case.