@J-Hilk It all looks fine to me as well, this is why it's even more difficult to find the issue. Oh well, guess I have to spend more time on this than I had planned to. Thanks for all your help tho, I highly appreciate it! :)

https://bugreports.qt.io/browse/QTBUG-135011 for anyone else encountering this, I have opened a bug with the upstream https://bugreports.qt.io/browse/QTBUG-135011

It's not worked also with any popup Widgets, Dialogs, Menus, Popups, etc. Also issue persist in the latest 6.8.3 and 6.9.0 and caused by this changes - https://codereview.qt-project.org/c/qt/qtbase/+/568225 (https://bugreports.qt.io/browse/QTBUG-135253) A created a separate issue, with steps how to reproduce it with the latest Qt version - https://bugreports.qt.io/browse/QTBUG-135253

https://www.youtube.com/watch?v=m7etOQfrMiM

I had the same problem (on other platforms as well). I fixed it by using a Flickable for my display object, and modifying the contentY property when I displayed the keyboard: flickable.contentY = Math.max(0, (yValue + (height / 2)) - ((flickable.height - inputPanelPopup.height) / 2)) You'll probably need to modify the algorithm for your application, but the idea should work.

@Gracy The question is pretty old, but i know the answer... First, make sure, the permissions are added. Maybe you are missing the following: https://doc.qt.io/qtcreator/creator-deploying-android.html#editing-manifest-files To check and request permissions you can do: QFuture permission_request = QtAndroidPrivate::requestPermission("android.permission.WRITE_EXTERNAL_STORAGE"); switch(permission_request.result()) { case QtAndroidPrivate::Undetermined: qWarning() << "Permission for writing to the storage undetermined!"; break; case QtAndroidPrivate::Authorized: qDebug() << "Permission for writing to the storage authorized"; break; case QtAndroidPrivate::Denied: qWarning() << "Permission for writing to the storage denied!"; break; }

@BILAL-KHAN-34 Put the mouse cursor over the yellow warning icon to see the pop-up with the information about the problem.

That was a nasty one. Glad you found out and thanks for sharing !

@gregory109 I tried: QtJniTypes::Context context = QNativeInterface::QAndroidApplication::context(); m_javaObject = QJniObject("org/qtproject/qt/android/purchasing/InAppPurchase", "(Landroid/content/Context;J)V", context, this); but it did not help. Looks like QtJniTypes::Context is not a trivial type defined with Q_DECLARE_JNI_CLASS(Context, "android/content/Context").

I had the same problem upgrading from 6.6 to 6.7, I resolved it by using the correct NDK (26.1.10909125), see https://doc.qt.io/qt-6/android-getting-started.html

@Sammasas I didn't find a universal way, but with an QJNIObject and objective c it works now. Java with JNiObject: package Klingelball; import android.content.Context; import android.content.res.Configuration; import android.util.DisplayMetrics; import android.view.WindowManager; public class AndroidSettings { public static float getFontScale(Context context) { //return getResources().getConfiguration().fontScale; Configuration configuration = context.getResources().getConfiguration(); // Get the font scale from the configuration float fontScale = configuration.fontScale; return fontScale; } } It's important that the file is under src/mypackage. .cpp file: #ifdef Q_OS_ANDROID QJniObject context = QNativeInterface::QAndroidApplication::context(); if(QJniObject::isClassAvailable("Klingelball/AndroidSettings")) { QJniObject androidSettingsJavaObject = QJniObject("Klingelball/AndroidSettings"); fontScale = new float(androidSettingsJavaObject.callStaticMethod<jfloat>("Klingelball/AndroidSettings", "getFontScale", "(Landroid/content/Context;)F", context.object<jobject>())); qDebug() <<"Font scale:" << *fontScale; setup_fontAndroid(*fontScale); } else { qDebug() << "JAVA CLASS UNAVAIABLE!"; fontScale = new float(1); setup_fontAndroid(*fontScale); } #endif iOs with objective-c: .mm file: include "iOSSettings.h" #include <UIKit/UIKit.h> int iOSSettings::getPrefferedFont() { return [UIFont preferredFontForTextStyle:UIFontTextStyleBody].pointSize; } .h file: class iOSSettings { public: static int getPrefferedFont(); }; .cpp file: #ifdef Q_OS_IOS fontScale = new float(getfontScalefrompointSize(iOSSettings::getPrefferedFont())); setup_fontiOS(iOSSettings::getPrefferedFont()); #endif iOS returns the preffered Fontsize, I implemented a function that returns a factor based on the fontsize because I had to scale the Icons too. Hope this helps somebody :)

@chenPeng First, you need to click Download OpenSSL Button to install android_openssl.

I had the same problem and solved it on Ubuntu by deleting the cache of QtCreator using : rm -R ~/.cache/QtProject

@SGaist did some more tests. removed some lines with errors from .pro and got some more output from qmake2cmake. but only for the easy parts ;-) android or ios - specific parts are missed. ATM I'm learning from CMakeLists.txt provided by Qt example apps, other projects and documentation. what's really missed: official guides for mobile (android and ios) apps (including translations, native code, custom info.plist, Android Manifest, openSSL) from build to deploy and publish to stores using CMake. of course I'll blog about my findings in some weeks.

@TheoSys File a bug to Qt and tell them to fix it.

@Bondrusiek I solved that. Do this steps: Select the "Projects" tab on the left. In the left side panel, select the "Build Android APK" section. Scroll down to the "Build Steps" section and find the "Packaging" step. In the "Packaging" section, you should see a "Sign package" checkbox. Make sure it's checked. Configure "Signing Configuration" with required information such as keystore file path, keystore password, key alias and key password. If you don't already have a keystore file, you can create one using the java keytool. Click the "Apply" button to save your changes. Now try building your Android APK again by clicking on the green arrow icon (or using Ctrl + B) in the lower left corner of Qt Creator.

@JoeCFD Thank you for your answer, but that was exactly what I had done - tried and tried all over again. The solution came now with vigorously erasing all of AndroidSDK, upgrading Creator. Now it works!! I'll probably never know why it didn't before. :-)

UPDATE: This is a known bug in Qt https://bugreports.qt.io/browse/QTBUG-113616