Consider implementing an Android class like Coils NetworkObserver

[yschimke]

Coil monitors networks and shortcircuits requests when no available network. It's on by default so the strategy seems solid.

https://github.com/coil-kt/coil/blob/01d96431ef588c3da08cc7ef4afbd3eb8b50b175/coil-base/src/main/java/coil/network/NetworkObserver.kt

https://github.com/coil-kt/coil/blob/01d96431ef588c3da08cc7ef4afbd3eb8b50b175/coil-base/src/main/java/coil/util/SystemCallbacks.kt

[swankjesse]

I think this makes more sense at Coil’s layer vs. OkHttp’s?

One problem I have with guards like this is their data is necessarily incomplete. The only way to know for sure whether an HTTP request will succeed is to attempt it! The network status is stale the moment it returns, and it only knows what’s inside the calling host and not the state of the rest of the network.

I do think there’s utility in things like this at the application layer, where you can tell the user that they’re offline and that they should turn on WiFi or whatever.

[yschimke]

I think this is feasible in okhttp-android. And might solve the airplane type issues.

#3278

[yschimke]

@swankjesse I think #8200 makes this look more valuable.

[yschimke]

Also https://developer.android.com/reference/android/net/ConnectivityManager.NetworkCallback#onBlockedStatusChanged%28android.net.Network,%20boolean%29

[yschimke]

Another example from Cronet

https://cs.android.com/android/platform/superproject/main/+/main:external/cronet/net/android/java/src/org/chromium/net/NetworkChangeNotifierAutoDetect.java;drc=15978b577cc30ad2c5b8f5e9d1cd5986ea7f09ae;l=635?q=f:chromium%20mDefaultNetworkCallback;

On change of default network, it will stop issuing pooled connections.