Details
-
Bug
-
Resolution: Unresolved
-
P2: Important
-
None
-
Qt Creator 16.0.0
-
None
Description
When turning the QmlDesigner plugin on, Windows asks if the user wants to allow Qt Creator to listen to network connections.
I suspect that is due to the new "DeviceManager" unconditionally listening on some UDP socket (though I haven't tried to confirm that):
1 QmlDesigner::DeviceShare::DeviceManager::initUdpDiscovery() devicemanager.cpp 60 0x12f2a4830 2 QmlDesigner::DeviceShare::DeviceManager::DeviceManager(QObject *) devicemanager.cpp 40 0x12f2a3ddc 3 QmlDesigner::DeviceShare::DeviceManager::DeviceManager(QObject *) devicemanager.cpp 36 0x12f2a52e8 4 QmlDesigner::QmlDesignerPluginPrivate::QmlDesignerPluginPrivate() qmldesignerplugin.cpp 172 0x12e6892d8 5 QmlDesigner::QmlDesignerPluginPrivate::QmlDesignerPluginPrivate() qmldesignerplugin.cpp 172 0x12e682ed8 6 QmlDesigner::QmlDesignerPlugin::initialize(QList<QString> const&, QString *) qmldesignerplugin.cpp 301 0x12e682738 7 ExtensionSystem::CppPluginSpec::initializePlugin() pluginspec.cpp 1315 0x100524a4c 8 ExtensionSystem::Internal::PluginManagerPrivate::loadPlugin(ExtensionSystem::PluginSpec *, ExtensionSystem::PluginSpec::State) pluginmanager.cpp 1874 0x1004cd890 9 ExtensionSystem::Internal::PluginManagerPrivate::loadPlugins() pluginmanager.cpp 1441 0x1004c2c88 10 ExtensionSystem::PluginManager::loadPlugins() pluginmanager.cpp 337 0x1004c2884 11 main main.cpp 951 0x10000e7a4 12 start (arm64e) /usr/lib/dyld 0x186188274
This doesn't really make a great impression, also because the user doesn't have any idea what this is about. It would be much better if that was only started when needed, and with some user interaction. The current behavior also leads to that feature to be broken, because chances are that users just do not give Qt Creator that permission, and are never asked again (for the same QtC installation in the same path). QDS is most probably affected in the same way.