Qt 5.15.2 Known Issues: Difference between revisions
(Created page with "Category:Known Issues *Check that your system meets [http://doc-snapshots.qt.io/qt5-5.15/gettingstarted.html#platform-requirements Qt's requirements] *All open issues can...") |
(→Qt for Device Creation: Added ebike demo issue) |
||
(2 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
[[Category:Known Issues]] | [[Category:Known Issues]] | ||
*Check that your system meets [http://doc-snapshots.qt.io/qt5-5.15/gettingstarted.html#platform-requirements Qt's requirements] | *Check that your system meets [http://doc-snapshots.qt.io/qt5-5.15/gettingstarted.html#platform-requirements Qt's requirements] | ||
*All open issues can be found from Jira: https://bugreports.qt.io | *All open issues can be found from Jira: https://bugreports.qt.io | ||
**RTA findings [https://bugreports.qt.io/issues/?filter=21874 here] | **RTA findings [https://bugreports.qt.io/issues/?filter=21874 here] | ||
== OpenSSL == | ==OpenSSL== | ||
Qt 5.15 | Qt 5.15 LTS requires OpenSSL 1.1.1 version on Linux and Windows. Qt online installer provides as convenience both OpenSSL source code and pre-built binaries of the OpenSSL libraries used by Qt Network. However, the installer doesn't set up OpenSSL environment. User needs to define the library path and possible environment variables. OpenSSL libraries are not automatically deployed with applications that are built with Qt. If provided OpenSSL binaries are not suitable for your use case source code installation includes instructions on how to configure and build your own OpenSSL libraries. | ||
Import and export restrictions apply for some types of software, and for some parts of the world. Developers wishing to use SSL communication in their deployed applications should either ensure that their users have the appropriate libraries installed, or they should consult a suitably qualified legal professional to ensure that applications using the code from the OpenSSL project are correctly certified for import and export in relevant regions of the world. | Import and export restrictions apply for some types of software, and for some parts of the world. Developers wishing to use SSL communication in their deployed applications should either ensure that their users have the appropriate libraries installed, or they should consult a suitably qualified legal professional to ensure that applications using the code from the OpenSSL project are correctly certified for import and export in relevant regions of the world. | ||
Line 11: | Line 12: | ||
See more instructions from {{Issue|QTCREATORBUG-22587}} | See more instructions from {{Issue|QTCREATORBUG-22587}} | ||
== All platforms == | ==All platforms== | ||
==Windows== | ==Windows== | ||
Line 19: | Line 19: | ||
==macOS== | ==macOS== | ||
==Android== | ==Android== | ||
Line 25: | Line 24: | ||
==iOS== | ==iOS== | ||
*{{Issue|QTCREATORBUG-24672}} When deploying to a device running iOS 14 then it will fail to connect, although the application is successfully deployed | |||
==UWP== | ==UWP== | ||
Line 33: | Line 34: | ||
==Qt for Device Creation== | ==Qt for Device Creation== | ||
==Qt for Automation 5.15 == | *Target debugging using a Windows host has an issue where gdb may run out of memory preventing further debugging (QTBUG-74349) | ||
*e-bike demo does not show map data in navigation view as the used map API has been deprecated (QTBUG-88640) | |||
==Qt for Automation 5.15== | |||
{{Release Information}} | {{Release Information}} |
Latest revision as of 07:57, 20 November 2020
- Check that your system meets Qt's requirements
- All open issues can be found from Jira: https://bugreports.qt.io
- RTA findings here
OpenSSL
Qt 5.15 LTS requires OpenSSL 1.1.1 version on Linux and Windows. Qt online installer provides as convenience both OpenSSL source code and pre-built binaries of the OpenSSL libraries used by Qt Network. However, the installer doesn't set up OpenSSL environment. User needs to define the library path and possible environment variables. OpenSSL libraries are not automatically deployed with applications that are built with Qt. If provided OpenSSL binaries are not suitable for your use case source code installation includes instructions on how to configure and build your own OpenSSL libraries.
Import and export restrictions apply for some types of software, and for some parts of the world. Developers wishing to use SSL communication in their deployed applications should either ensure that their users have the appropriate libraries installed, or they should consult a suitably qualified legal professional to ensure that applications using the code from the OpenSSL project are correctly certified for import and export in relevant regions of the world.
See more instructions from QTCREATORBUG-22587
All platforms
Windows
Linux
macOS
Android
iOS
- QTCREATORBUG-24672 When deploying to a device running iOS 14 then it will fail to connect, although the application is successfully deployed
UWP
QNX
WebAssembly
Qt for Device Creation
- Target debugging using a Windows host has an issue where gdb may run out of memory preventing further debugging (QTBUG-74349)
- e-bike demo does not show map data in navigation view as the used map API has been deprecated (QTBUG-88640)