Even if we wanted to move to connectivity-api, we would need to fix those.
After looking further atks the connectivity-api, it is quite limited and cannot even detect when network is using mobile data or wifi.
We could:
* Use connectivity-api knowing that bearer functionality will be mostly broken, but should allow basic bearer use, and allow QNAM & friends to function unhindered.
I tried a working connectivity-api bearer plugin (verified with unconfined test app) with the attached example app, and I still got app armor errors:
Syslog> Jan 21 06:55:34 ubuntu-phablet dbus[1809]: apparmor="DENIED" operation= "dbus_method_ call" bus="session" path="/ com/ubuntu/ connectivity1/ NetworkingStatu s" interface= "org.freedeskto p.DBus. Properties" member="GetAll" mask="send" name="com. ubuntu. connectivity1" pid=11241 label=" com.ubuntu. developer. mzanetti. nmsessiontest_ myapp_0. 1" peer_pid=2631 peer_label= "unconfined"
Even if we wanted to move to connectivity-api, we would need to fix those.
After looking further atks the connectivity-api, it is quite limited and cannot even detect when network is using mobile data or wifi.
We could:
* Use connectivity-api knowing that bearer functionality will be mostly broken, but should allow basic bearer use, and allow QNAM & friends to function unhindered.
* add some functionality to connectivity-api