Hi, I am trying to deploy an app on the Play store. When I set the Cmake configuration to QT_ANDROID_BUILD_ALL_ABIS to true, I get the following warning which causes my application to crash because it tries to use one of these dependencies Skipping C:/Qt/6.8.3/android_armv7/plugins/multimedia/libplugins_multimedia_ffmpegmediaplugin_armeabi-v7a.so due to unmet dependencies: lib/libavcodec.so,lib/libavformat.so,lib/libavutil.so,lib/libswresample.so,lib/libswscale.so Skipping plugins/multimedia/libplugins_multimedia_ffmpegmediaplugin_armeabi-v7a.so due to unmet dependencies: lib/libavcodec.so,lib/libavformat.so,lib/libavutil.so,lib/libswresample.so,lib/libswscale.so Skipping C:/Qt/6.8.3/android_x86/plugins/multimedia/libplugins_multimedia_ffmpegmediaplugin_x86.so due to unmet dependencies: lib/libavcodec.so,lib/libavformat.so,lib/libavutil.so,lib/libswresample.so,lib/libswscale.so Skipping plugins/multimedia/libplugins_multimedia_ffmpegmediaplugin_x86.so due to unmet dependencies: lib/libavcodec.so,lib/libavformat.so,lib/libavutil.so,lib/libswresample.so,lib/libswscale.so Skipping C:/Qt/6.8.3/android_x86_64/plugins/multimedia/libplugins_multimedia_ffmpegmediaplugin_x86_64.so due to unmet dependencies: lib/libavcodec.so,lib/libavformat.so,lib/libavutil.so,lib/libswresample.so,lib/libswscale.so Skipping plugins/multimedia/libplugins_multimedia_ffmpegmediaplugin_x86_64.so due to unmet dependencies: lib/libavcodec.so,lib/libavformat.so,lib/libavutil.so,lib/libswresample.so,lib/libswscale.so When I build for a single architecture, I do not get that warning and my app runs fine. I am using QT 6.8.3 building on Windows 11. Any ideas?

@KroMignon said in The code execution cannot proceed because Qt6Core.dll was not found. Reinstalling the program may fix this problem.: By using deployment tool ==> https://doc.qt.io/qt-6/windows-deployment.html this thing doesn't opens. And why I need to open some other exes like this and trying to find how to use it, instead of just sharing exe directly from debug folder like it was in 5.15.16 version?

AFAIK this should work but it will not be visible in Assets tab but rather in Components: [image: 4bac87b2-d7be-4ed2-96d3-7e5911dc4694.png] Moreover, I just tried that with your configuration and the file generated was not empty. Honestly, I do not know what might have happened, your best bet is creating a ticket and attaching the .fig and .qtbridge files.

I'm getting the following error when I run "Squish for Qt 9.0.0" squishrunner.exe : Found invalid metadata in lib ../dlls/qt/imageformats/qgif.dll: Invalid metadata version Using qtplugininfo I get the following metadata for the file: qtplugininfo .\imageformats\qgif.dll IID "org.qt-project.Qt.QImageIOHandlerFactoryInterface" Qt 6.8.0 (release) User Data: { "Keys": [ "gif" ], "MimeTypes": [ "image/gif" ] } Finally, the Squish installation buildinfo.txt file: Package Name: squish-9.0.0-qt68x-win64-msvc143 Internal Name: /home/autotest/public_html/binpackages/2025/02/28-1700/bin_package/9.0.0/qt/Teufelsbek-Qt6.8.0binary-TkNone-iOSNone-MSVC143x64-fcaab59 Git Branch: 9.0.0 Git Revision: 239e98e6029aa13633774415f0c38f3d47257f2d Python Version: default Patched: False Debug Build: False Debug Symbols: False Pure Qt4 Build: False Include IDE: True Python 2: S:/binPackage/Python/x64/2.7.10binary_ssl Python 3: S:/binPackage/Python/x64/3.10.6binary Tcl: S:/binPackage/tcl/x64/8.6.4 Perl: S:/binPackage/Perl/x64/5.34.0 Ruby: S:/binPackage/Ruby/x64/2.5.3 My build environment is Qt 6.8.2 and MSVC 2022 for a 64-bit target.

Hey there! Thank you for taking the certification and giving your feedback on the test! The results can take up to two weeks to approve, whilst the results and proctoring of the exam take place, so please keep an eye out for your results in the meantime.

Solved by myself. I found "-utf-8" in two .conf files..

@dharani Hi. This is really a forum for users of Qt. For questions about the commercial license you should ask The Qt Company themselves, and that is presumably where you would get your licensed upgrade version from when you come to download.

Hi @RokeJulianLockhart, just some additional thoughts to consider... Kubuntu is an official "flavor" of Ubuntu. That is, its supported by Ubunutu, and has the same LTS and non-LTS releases Ubuntu has. KDE Neon is based-on an LTS Ubuntu, but is not supported by Ubuntu. It contains more recent KDE components, and is maintained (not sure about supported) by KDE devs. So there's definitely pro's and con's to both. But I'm sure both are good either way. I ask about Kubuntu explicitly because it's Qt-based, being the KDE Plasma variant, so I prefer it for verifying Qt bugs. While KDE is Qt-based, it actually uses Qt-derived libs, rather than Qt per se. So while it really doesn't matter, if you really like to use Qt on Ubuntu (as I do), then I can recommend Lubuntu, which is also an official Ubuntu flavour (supported by Ubuntu), but using the LXQt desktop by default instead. LXQt is a lightweight Qt-based desktop environment, so much more Qt-pure than KDE is (though again, it really doesn't matter). It's certainly not as feature rich as KDE, but then its without KDE's bloat too. LXQt suits my needs perfectly (by largely staying out of my way), but of course might not be right for you. Worth knowing about anyway. Cheers.