A modern programming language that makes developers happier.

kotlinlang

:wave: just looking at the experimental network monitor APIs, would it be possible to create a new `ApolloException` type for the offline exception used in `RetryOnErrorInterceptor` so that we can handle this in a type-safe way?

That makes sense. Also perfect timing cause it's related to <@U010JQZ3FRC> question above. Introducing new exception classes means if you were filtering on `ApolloNetworkException` before then you'll end up logging a bunch of "network is offline" exceptions

(looking forward to <https://youtrack.jetbrains.com/issue/KT-68296/Union-Types-for-Errors>)

What we could maybe do is add a cause to the `ApolloNetworkException` , that'd probably be transparent enough for existing users

Just not sure if there's something like this already or if we need to roll our own `IOException`

nice, a cause would be fine for our use case :+1:

<https://github.com/apollographql/apollo-kotlin/issues/6101>