Qt for Android known issues

Qt for Android known issues

• When running an application for arm64-v8a from Qt Creator, you may encounter the error "clang++.exe: error: no such file or directory: 'E:\android-ndk-r18b/sources/cxx-stl/llvm-libc++/libs/arm64-v8a/libc++.so.16'". This can be worked around by editing the build environment in the project settings and changing the environment variable ANDROID_NDK_PLATFORM to "android-21"
• The Android SDK tools do not work together with Oracle's JDK 9 on Windows. If you see errors such as "Android build SDK not defined. Check Android settings." when building a project, install an older JDK instead.
• There is a bug in GCC in the latest Android NDK, making it impossible to use it for building Qt. For Qt 5.12, the clang toolchain should be used, and is used by the official binary packages. For older versions, please use Android NDK r10e, which does not have the relevant gcc bug. NDK r15 produces applications that fail with the error message 'This application failed to start because it could not find or load the Qt platform plugin "android"'. See also the bug report.
• The Android NDK compiler has a bug when building for armv5 and deploying on older kernels. This will cause Qt applications to crash on startup. When building Qt, you need to disable 64-bit atomics for armv5. See QTBUG-52923 for more information.
• On Android 5.0 and later versions, the deployment option "Deploy local Qt libraries to temporary directory" in Qt Creator is not working correctly due to changes in the platform. There is currently no known work-around for this. Issues have been raised in the Android project here: https://code.google.com/p/android/issues/detail?id=79480
• WebKit is not supported
• Qt Quick 1 apps must be deployed using qrc (QTBUG-32170)
• Windows has a limitation on path lengths which can cause problems when your project is installed into a location with a very long path name. If you experience FileNotFoundException in openAsset() on startup of your application, try moving it to a directory with a shorter path.
• By default the Back key will terminate Qt for Android apps, unless the key event is accepted. Unfortunately, due to misleading documentation (QTBUG-35155), many applications (including Qt examples) are incorrect, and will block the back key. We recommend making the logic explicit: always accept() the Key_Back event, and quit() the application explicitly if required.
• The Qt Multimedia Widgets module is not supported on Android, which means video display is only available using the VideoOutput and Video QML items.
• On Kindle Fire 1st generation, there is a limitation on the number of libraries that can be loaded which will lead to shader compilation errors when running some Qt Quick apps. Apps that exhibit this bug will be rejected from being published to the Amazon market. A work-around for the issue is to reduce the number of libraries that are loaded, e.g. by deleting some image format plugins that are not required. See QTBUG-33264 for more information.
• With the first edition of Samsung XCover 3 (SM-G388F) there appears to be an issue with the graphics driver, causing Qt applications to crash when they are resumed after being suspended. Current investigation points towards a threading issue in the software on the device itself. The issue does not occur with the second edition of the same device, SM-G389F. There is no known work-around for this at the moment, so the recommendation is to blacklist this particular device model in Google Play. Setting the QML_BAD_GUI_RENDER_LOOP environment variable to 1 will make the crash less likely to occur. QTBUG-55392
• There are issues with the updated Android SDK which makes it impossible to use it together with earlier versions of Qt for Android. This has been fixed in Qt 5.9.0, but for older versions, it is possible to use the following links to download a working version of the SDK (do not update the SDK after downloading): macOS Windows and Linux.