Qt QML on VS Code complains about having correct corresponding revisions

Question

The Qt Qml extension on VS Code keeps reporting:

/usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick.2/plugins.qmltypes:(row):(column): Meta object revision and export version differ.
Revision (x) corresponds to version 0.(x); it should be 2.0.

This occurs everywhere the line: exportMetaObjectRevisions: [0] is found.

Note: Debian 13 and Qt 5.15 are used.

What I have tried:

Defining specific include paths inside the extension's settings
changing the number in the problematic line exportMetaObjectRevisions: [0] to 2, 2.0, and "2.0" which didn't work
I have tried using qmlplugindump to rebuild it however it reports another error (QtQml.WorkerScript not installed) which belongs in its own question.

Edit: It turns out qt5 doesn't seem to have any form of qmlls, but qt6 does. Any explanations for why it still worked and why it reported these errors will be accepted

Manraj Singh · Accepted Answer · 2025-09-11 12:41:21Z

0

Qt’s QML engine and tooling expect meta object revisions in .qmltypes files to match their export version.
Your system-installed Qt QML modules (/usr/lib/x86_64-linux- gnu/qt5/qml/QtQuick.2/plugins.qmltypes) have exportMetaObjectRevisions: [0] but the tooling expects it to be [2] (i.e., version 2.0).
This inconsistency triggers the warning in VS Code’s QML extension.

To fix or suppress it
Check Qt version compatibility

Make sure the Qt version used by VS Code extension matches the installed Qt version.

Run qmake -v or qtpaths --version to see your Qt version.
Check the VS Code QML extension documentation or settings for Qt version compatibility.

You can also try reinstalling QT because sometimes Updating or reinstalling QT packages fixes the mismatches.

answered Sep 11 at 12:41

Manraj Singh

575 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

JarMan Sep 11 at 15:22

This sounds like an answer written by AI. Be careful trusting anything that is AI-generated.

none2 · Accepted Answer · 2025-09-19 18:26:20Z

0

As it turns out: I hadn't properly told the extension where to find qmlls. It's not in the path it would expect it to be, but it was actually in /usr/bin/qmlls6. After setting the custom exe path to that, I got no more errors

answered Sep 19 at 18:26

none2

356 bronze badges

Collectives™ on Stack Overflow

Qt QML on VS Code complains about having correct corresponding revisions

2 Answers 2

1 Comment

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Related