Commit f5aecbde9138b9bdde4c747cb6c7e8f145e96630 breaks context properties that have the same name as a registered QML type (at least that's my working theory ).

Currently qtapplicationmanager is stuck in sub-module integration because of this issue:

• We have a class ApplicationInterface that is registered declaratively via a foreign class: https://code.qt.io/cgit/qt/qtapplicationmanager.git/tree/src/qml/qtapplicationmanager_application_p.h#n29
• Instances of this class get set as a context property for in-process apps started by the appman: https://code.qt.io/cgit/qt/qtapplicationmanager.git/tree/src/manager-lib/qmlinprocruntime.cpp#n106
• Later on, applications fail to connect to signals of these instances in the unit tests, simply because the context property is null (had to add a console.warn in an Component.onCompleted handler to find that out) https://code.qt.io/cgit/qt/qtapplicationmanager.git/tree/tests/auto/qml/simple/apps/tld.test.simple2/app.qml#n18
• If I rename the context property to XApplicationInterface and use that name in the Connections element of the application, it works perfectly fine again. It seems like there's a clash between the type name and the context property name?

I did look into that commit, but couldn't see anything obvious jumping out at me.