core/network — HTTP Networking

To handle Dio 401 token refresh safely, this Skill uses an Auth interceptor with queued token refresh logic, ensuring concurrent authenticated API requests wait for a single refresh cycle to complete before retrying.

You map HTTP network errors to app-level exceptions using a dedicated Error interceptor that catches Dio errors and converts them into typed app exceptions for reliable Flutter data layer handling.

The best way to check offline connectivity is using a NetworkInfo abstraction over connectivity_plus, which checks online status and streams connectivity changes to prevent API requests when offline.

You set up a singleton Dio client using a central factory to create the instance with base options and ordered interceptors: Auth, then Error, then conditional Logging for debug builds.

Yes, you need FlutterSecureStorage because the network stack initialization requires passing a FlutterSecureStorage instance to the factory to securely manage tokens for authenticated API requests.

Flutter API calls fail on network drops without a connectivity guard; this Skill provides timeout handling and a NetworkInfo abstraction using connectivity_plus to observe connectivity changes and avoid offline requests.