Qt 6.2.4 app does not detect any TLS/SSL backend (edit: works well with Qt 6.3.0rc)

Mitsuriou

Hello,

I have migrated my app to Qt 6.2.4, coming from 5.15.2 (https://github.com/Mitsuriou/MFBO-Preset-Creator/tree/qt-6-compat).
Everything works fine in both Visual Studio 2022 & Qt Creator 7.0.0, with both MSVC and MinGW, but when I deploy my app, the SLL support does not work.
Just to be sure, I've redeployed all the dependencies many times with

> D:\Qt\6.2.4\msvc2019_64\bin\windeployqt.exe .\MFBOPresetCreator.exe --release --compiler-runtime

I've updated and tried with the latest OpenSSL DLLs for windows, I've tried with the ones Qt provides from the Qt Installer... But nothing works.
I've noticed that there is a new folder named "tls" next to my .exe now, which contains 3 backend DLLs.
When I check in standalone mode, my .exe does not find any SSL backend at runtime (but as I said, it works in VS 2022 and Qt Creator).

With the code below in my main.cpp file:

    Utils::PrintMessageStdOut("");
    Utils::PrintMessageStdOut("Running MFBOPC in debug mode");
    Utils::PrintMessageStdOut("Checking support for SSL...");

    const auto lAvailableBackends{QSslSocket::availableBackends()};
    for (const auto& lBackend : lAvailableBackends)
    {
      Utils::PrintMessageStdOut(QString("Found SSL backend \"%1\"").arg(lBackend));
    }

    Utils::PrintMessageStdOut(QString("SSL backend: ").arg(QSslSocket::activeBackend()));
    Utils::PrintMessageStdOut(QString("Supports SSL? %1").arg(QSslSocket::supportsSsl() ? "yes" : "no"));
    Utils::PrintMessageStdOut(QString("SSL version information: %1").arg(QSslSocket::sslLibraryBuildVersionString()));
    Utils::PrintMessageStdOut("");

I get the result below in my console:

Running MFBOPC in debug mode.
Checking support for SSL...
SSL backend: .
Supports SSL? no.
SSL version information: .

Could this be a bug with Qt 6.2.4? I've seen two or three recent posts already, on Internet, but there was not any solution to my issue.

Mitsuriou

EDIT: The same code works very well with Qt 6.3.0rc.
I'm quite sad that I lost so much time just for a thing that was not on my side ^^'

Little question: should I report the issue to Qt? If yes, how do I do that?

SGaist

Hi,

If you can reliably trigger this issue, then yes please report it with a full minimal compilable example that shows how to trigger it.