You are always free to ignore the network status. It was moved in mainly as a convenience feature, to allow a scope to immediately notice if, for example, the device is in flight mode. Given the problems with NetworkAccessManager (still not completely resolved), I would probably interpret "unknown" to mean "available" and go ahead, and only pay attention if the status indicates "network down".
The issue with ActionMetadata and PerformAction not receiving the network status needs looking at. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1502282 Title: "unknown" connectivity status problematic To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1502282/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
