如何修复android.os.DeadObjectException机器人X [英] How to fix android.os.DeadObjectException android X

问题描述

当机器人解除我创建了一个服务（service.MyService），我看到了 下面DeadObjectException。

When android unbind a service I created (service.MyService), I see the following DeadObjectException.

你能告诉我怎么这是什么意思，我可以解决这个例外？

Can you please tell me how what does this mean and can I fix this exception?

W/ActivityManager(  583): Exception when unbinding service
com.mycompany/.service.MyService
W/ActivityManager(  583): android.os.DeadObjectException
W/ActivityManager(  583):       at
android.os.BinderProxy.transact(Native Method)
W/ActivityManager(  583):       at
android.app.ApplicationThreadProxy.scheduleUnbindService(ApplicationThreadNative.java:516)
W/ActivityManager(  583):       at
com.android.server.am.ActivityManagerService.removeConnectionLocked(ActivityManagerService.java:9609)
W/ActivityManager(  583):       at
com.android.server.am.ActivityManagerService.killServicesLocked(ActivityManagerService.java:8515)
...

感谢你。

推荐答案

这意味着，您的服务已停止 - 无论是从OS杀害，或者从您的应用程序停止

This means that your service had already stopped - either killed from the OS, or stopped from your application.

这是否会发生的问题每次调试你的项目？

Does this problem happen every time you debug your project?

重写你的服务的的onDestroy（）方法，看导致它什么事件流。如果赶上 DeadObjectException 无需通过这种方法，你的服务应该被杀害的操作系统。

Override your service's onDestroy() method and watch what event flow leads to it. If you catch DeadObjectException without going through this method, your service should have been killed by the OS.

这篇关于如何修复android.os.DeadObjectException机器人X的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！