Flutter already has a connectivity monitoring mechanism which is what our ConnectivityMonitor leverages.
ConnectivityMonitor doesn't provide any actual connectivity monitoring in neither rollbar_common nor rollbar_dart.
The Flutter implementation doesn't offer any feature that Flutter's own stdlib does not, and obfuscates information the user may need such as the type of network connectivity achieved.
Internally, it was being used to make our code believe there was no connectivity for a certain amount of time after an http transaction failed, in order to delay new http transaction attempts.
Flutter already has a connectivity monitoring mechanism which is what our ConnectivityMonitor leverages.
ConnectivityMonitor doesn't provide any actual connectivity monitoring in neither
rollbar_commonnorrollbar_dart.The Flutter implementation doesn't offer any feature that Flutter's own stdlib does not, and obfuscates information the user may need such as the type of network connectivity achieved.
Internally, it was being used to make our code believe there was no connectivity for a certain amount of time after an http transaction failed, in order to delay new http transaction attempts.