Martin Devillers
12/18/2018, 3:13 PMwithContext
and CompletableDeferred
.[Failed]
exception which is thrown by the exception handler (which mimicks the default behavior on the Android platform by causing a crash).
By completing a CompletableDeferred
exceptionally after a timeout waiting for it, the exception gets propagated to the uncaught exception handler. I wouldn’t expect this, given the documentation of CompletableDeferred.completeExceptionally
completeExceptionally
changes simply due to the fact that await
has been called on it, then cancelled. If await
isn’t called, then there isn’t any failure.completeExceptionally
, and there’s no way to know whether a crash will be caused when calling this method. I suspect a bug. If anybody can provide more insight on this, it would be greatly appreciated.develop
branch)