Added in API level 1

DeadObjectException


open class DeadObjectException : RemoteException
kotlin.Any
   ↳ kotlin.Throwable
   ↳ java.lang.Exception
   ↳ android.util.AndroidException
   ↳ android.os.RemoteException
   ↳ android.os.DeadObjectException

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 threw 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 one-way call queue filling up (too many one-way 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.

Summary

Public constructors

Inherited functions

Public constructors

DeadObjectException

Added in API level 1
DeadObjectException()

DeadObjectException

Added in API level 23
DeadObjectException(message: String!)