This is particularly vicious because I don’t see a...
# coroutines
m
This is particularly vicious because I don’t see any way to work around this issue. There’s no way to catch it when it’s thrown by the call to
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.