Qt for Android known issues: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
No edit summary
(This page no longer contains specific information for each individual version, which was kind of confusing anyway. We should rather just maintain a list of current information which is useful)
Line 1: Line 1:
== Qt for Android known issues in 5.7.0 ==
== Qt for Android known issues in 5.7.0 ==
=== General ===
* The JAR files for QtAccessibility have been merged with the main JAR files for Qt. For most users this will not require any action, but if you have custom deployment scripts that mention the removed files, these will have to be updated.
* The JAR files for QtAccessibility have been merged with the main JAR files for Qt. For most users this will not require any action, but if you have custom deployment scripts that mention the removed files, these will have to be updated.
* There is a bug in GCC in the latest Android NDK, making it impossible to use it for building Qt. The bug has been fixed in Android NDK r12, available as beta [https://github.com/android-ndk/ndk/wiki#current-beta-release here]. See also [https://github.com/android-ndk/ndk/issues/67 the bug report].
* There is a bug in GCC in the latest Android NDK, making it impossible to use it for building Qt. The bug has been fixed in Android NDK r12, available as beta [https://github.com/android-ndk/ndk/wiki#current-beta-release here]. See also [https://github.com/android-ndk/ndk/issues/67 the bug report].
* The Android NDK compiler has [https://code.google.com/p/android/issues/detail?id=58476 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 [https://bugreports.qt.io/browse/QTBUG-52923 QTBUG-52923] for more information.   
* The Android NDK compiler has [https://code.google.com/p/android/issues/detail?id=58476 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 [https://bugreports.qt.io/browse/QTBUG-52923 QTBUG-52923] for more information.   
== Qt for Android known issues in 5.4.0 ==
=== General ===
* On Android 5.0, neither the debug deployment or Ministro are 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=79478 https://code.google.com/p/android/issues/detail?id=79480
* On Android 5.0, neither the debug deployment or Ministro are 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=79478 https://code.google.com/p/android/issues/detail?id=79480
* WebKit is not supported
* WebKit is not supported
Line 17: Line 13:
* The Android 5.0 Material theme is not fully supported (QTBUG-42520)
* The Android 5.0 Material theme is not fully supported (QTBUG-42520)
* Qt Quick Controls text selection handles may appear below other controls (QTBUG-42538) ==
* Qt Quick Controls text selection handles may appear below other controls (QTBUG-42538) ==
== Qt for Android known issues in 5.3.2 ==
=== General ===
* On Android 5.0, step-by-step debugging and debug deployment in Qt Creator is not working correctly due to changes in the platform. There is currently no known work-around for this.
* WebKit is not supported
* Qt Quick 1 apps must be deployed using qrc (QTBUG-32170)
* When using the Qt SDK, Qt Creator's Android settings will warn that "Qt version for architecture mips is missing". This is because MIPS is not currently a supported version of the Qt for Android SDK.
* 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.
* Due to the same path length limitation on Windows, you may experience compilation errors of the form "No rule to make target …/…/../etc." when building Qt examples. A possible work-around for this is to put the build directory for the project behind a shorter path (for instance by turning off shadow building for the project in Qt Creator). (QTBUG-37113)
* By default the Back key will terminate Qt for Android apps, unless the key event is accepted. In Qt 5.2.0, this also applies to the key press event. 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.
* Due to a bug in the Android NDK (http://code.google.com/p/android/issues/detail?id=71396 ) on Mac OS X, the gdb in the later official NDKs cannot be used with Qt Creator. You can get a replacement in the following location: http://download.qt.io/official_releases/gdb/osx/ ==
=== Selected bugs ===
* QTCREATORBUG-12331: There is a regression in the gdb contained in newer versions of the Android NDK on Mac OS X. A patch has been submitted and is currently pending, but currently an older NDK version is required to debug Android applications in Qt Creator on OS X.

Revision as of 13:28, 10 May 2016

Qt for Android known issues in 5.7.0

  • The JAR files for QtAccessibility have been merged with the main JAR files for Qt. For most users this will not require any action, but if you have custom deployment scripts that mention the removed files, these will have to be updated.
  • There is a bug in GCC in the latest Android NDK, making it impossible to use it for building Qt. The bug has been fixed in Android NDK r12, available as beta here. 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, neither the debug deployment or Ministro are 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=79478 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)
  • When using the Qt SDK, Qt Creator's Android settings will warn that "Qt version for architecture mips is missing". This is because MIPS is not currently a supported version of the Qt for Android SDK.
  • 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. In Qt 5.2.0, this also applies to the key press event. 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.
  • The Android 5.0 Material theme is not fully supported (QTBUG-42520)
  • Qt Quick Controls text selection handles may appear below other controls (QTBUG-42538) ==
Retrieved from "https://wiki.qt.io/index.php?title=Qt_for_Android_known_issues&oldid=23920"