DeadObjectException Class

Definition

[Android.Runtime.Register("android/os/DeadObjectException", DoNotGenerateAcw=true)]
public class DeadObjectException : Android.OS.RemoteException

[<Android.Runtime.Register("android/os/DeadObjectException", DoNotGenerateAcw=true)>]
type DeadObjectException = class
    inherit RemoteException

Inheritance

Exception

Throwable

Exception

AndroidException

RemoteException

DeadObjectException

Derived

Android.OS.DeadSystemException

Attributes

RegisterAttribute

Remarks

The object you are calling has died, because its hosting process no longer exists, or there has been a low-level binder error.

If you get this exception from a system service, the error is usually nonrecoverable as the framework will restart. If you receive this error from an app, at a minimum, you should recover by resetting the connection. For instance, you should drop the binder, clean up associated state, and reset your connection to the service which through this error. In order to simplify your error recovery paths, you may also want to "simply" restart your process. However, this may not be an option if the service you are talking to is unreliable or crashes frequently.

If this isn't from a service death and is instead from a low-level binder error, it will be from: - a oneway call queue filling up (too many oneway calls) - from the binder buffer being filled up, so that the transaction is rejected.

In these cases, more information about the error will be logged. However, there isn't a good way to differentiate this information at runtime. So, you should handle the error, as if the service died.

Java documentation for android.os.DeadObjectException.

Portions of this page are modifications based on work created and shared by the Android Open Source Project and used according to terms described in the Creative Commons 2.5 Attribution License.

Constructors

Fields

Properties

Methods

Explicit Interface Implementations

Extension Methods

Applies to