We've recently discovered that the QML code editor in Qt Creator 14.0 and 15.0 is not working as expected out of the box. The QML Language Server integration is currently broken, and we'd like to address it openly and provide solutions for those affected.

Qt projects targeting Qt 6.8 have lots of warnings when opened in Qt Creator, despite still building and running fine. The problem was introduced while transitioning Qt Creator from the embedded codemodel to QML Language Server.

In Qt Creator 14.0, we introduced the QML Language Server as the default mechanism for features such as warnings, autocompletion, and navigation ("Go to Definition"). While this modern integration offers numerous benefits, it relies on build folder information to resolve user-defined or custom QML modules. This information is essential for accurate imports and proper functionality.

Due to an oversight on our part, the necessary build folder data was not passed to the QML Language Server. As a result, many projects show incorrect warnings, and key features like autocompletion and navigation are not working as intended.

If you're using Qt Creator 14.0 or 15.0 with projects that include custom or user-written QML modules:

Even with the above issues, your projects will still build and run correctly. We will provide a permanent fix for these issues. The next section describes a workaround to improve your situation right now.

To mitigate this issue, we recommend the following workarounds until Qt Creator 16 is released:

You can manually provide the missing build folder information to the QML Language Server via CMake. To achieve that:

Note that is not yet supported on Boot2Qt projects.

You can enable the embedded code model by disabling QML Language Server in the Qt Creator settings,. This allows to use the older system for warnings, autocompletion, navigation, and other features, but has the drawback that some of the "real warnings" won't be shown in that case.

The upcoming Qt Creator 16.0 will include a reworked QML Language Server integration, ensuring that the necessary build folder information is passed correctly. This will restore functionality and resolve the current issues.

We are also reviewing our internal processes to ensure that such oversights will be identified as early as possible and avoided in the future so that they don't impact you as users.

We apologize for the inconvenience and confusion this issue may have caused. We greatly value your feedback and appreciate your understanding as we work to improve Qt Creator and deliver the experience you deserve.

If you have any questions or need further assistance, please don't hesitate to reach out to us.