Mobile and Embedded

I have worked around this by using "adjustNothing" and get keyboard geometry from Java code.

Seems the flag issue was caused by a Magisk module replacing sytem emoji by iOS emoji. Without that module flags are fine.

It seems a bug indeed. When I build with Qt6.7.3 the anchors are positioned correctly.
I created this bug report: https://bugreports.qt.io/browse/QTBUG-133993

I encountered a similar problem in my effort to port a desktop app (developed on Ubuntu 20 / Qt 6.8.0) to Android. The problem seems to have gone away for me when I removed all the vertical spacers from the layouts within my QDialog.

@jsulm The compilation is now stuck in the image below.
e3c07b77-61f8-4c59-ba8c-8be4fa157a1a-image.png
What can I do?

@InsideFPV said in Error 127 while debugging qgroundcontrol code.:

i am not understand about compiler configuration please more explain about this

Simply click on the Compiler tab in Kit configuration page in settings (next to "Qt Versions"), select your compiler for Android and check the path to the compiler there...
As you can see from the error message the compiler cannot be found and if you look at the used path it is clearly wrong (slashes are missing).

You've tried what exactly?

You shouldn't need to switch to Linux.
What is strange is that the error message seems to indicate that the .so file is not in the path you gave.

@lukas_kosinski and @biskero ,
I use SCodes in my application and find:

It works perfectly with Qt5.15.18 on Windows and Android It works perfectly with Qt6.2.13 on Windows It fails to work with Qt6.2.13 on Android.
With the latter, I get this error: Cannot make QOpenGLContext current in a different thread
I have left further details about this issue on the github site of SCodes.

@IMAN4K

Hi,
similar problem exists here.
Did you eventually found a solution for the problem, that you remember?

I run into it on a buildroot issue without desktop manager.
Currently I suspect a problem with the interpreting system input events by QApplication.
Seems that QGuiApplication does something different.

@jsulm yes sir i have installed it

For those who got here in desperate search of answer...

qt_import_plugins(${PROJECT_NAME} EXCLUDE_BY_TYPE platforms)

this disables linking of the platform plugin in Qt6::Gui, therefore solving the error.
Because most probably you link the module in order to work with colours or something like this.
The qt_import_plugins can be even more refined. If you are interested, just google it.

Sorry to answer to this old topic.
I spent days to make it work now, without success, because the Qt virtual keyboard documentation (https://doc.qt.io/qt-5/qtvirtualkeyboard-index.html) promises:

Supports both Qt Quick and Qt Widgets applications.

So why are they saying that, when there is no way/layer/instance to run a pure a "Qt Widgets application" with a qt virtual keyboard?

Did it come to there mind that people eventually don't want to reinvent there c++ code to qml ?

I use cmake directly and successful. This is my configure:

cmake -S ../.. ^ -G Ninja ^ -DCMAKE_BUILD_TYPE=Debug ^ -DBUILD_SHARED_LIBS=OFF ^ -DFEATURE_static_runtime=ON ^ -DCMAKE_INSTALL_PREFIX="C:/Library/QT/6.8.1/VS2019/x64-debug-static" ^ -DBUILD_qtdoc=OFF ^ -DBUILD_qtwebengine=OFF ^ -DBUILD_qtwebview=OFF ^ -DBUILD_qtwayland=OFF ^ -DBUILD_WITH_PCH=OFF ^ -DQT_INTERNAL_CALLED_FROM_CONFIGURE:BOOL=TRUE ^ -DQT_QMAKE_TARGET_MKSPEC=win32-msvc ^ -DCMAKE_C_COMPILER=cl ^ -DCMAKE_CXX_COMPILER=cl ^ -DQT_BUILD_TESTS=FALSE ^ -DQT_BUILD_EXAMPLES=FALSE ^ -DFEATURE_cxx20=OFF ^ -DFEATURE_cxx2b=OFF ^ -DFEATURE_ssl=ON ^ -DINPUT_openssl=linked ^ -DFEATURE_system_zlib=ON ^ -DFEATURE_system_sqlite=ON ^ -DINPUT_libpng=system ^ -DINPUT_libjpeg=system ^ -DINPUT_freetype=system ^ -DINPUT_harfbuzz=system ^ -DINPUT_pcre=system ^ -DINPUT_doubleconversion=system ^ -DINPUT_webp=system ^ -DINPUT_tiff=system ^ -DFEATURE_icu=ON ^ -DFEATURE_gif=ON ^ -DFEATURE_ico=ON ^ -DFEATURE_vulkan=OFF ^ -DFEATURE_xcb=OFF ^ -DFEATURE_egl=OFF ^ -DFEATURE_libudev=OFF ^ -DFEATURE_slog2=OFF ^ -DFEATURE_dbus=OFF ^ -DCMAKE_CXX_STANDARD=17 ^ -DCMAKE_C_STANDARD=11 ^ -DCMAKE_EXE_LINKER_FLAGS="brotlicommon.lib brotlidec.lib brotlienc.lib bz2d.lib deflatestatic.lib libsharpyuv.lib lzma.lib rpcrt4.lib usp10.lib"

The key should be to specify libs using CMAKE_EXE_LINKER_FLAGS

I've got the same problem and this is with the qmlvideo example.
In order to get the thing to link, I had to edit QT_OSX_ARCHITECTURES to remove the x86_64 part.
It's a bit of a hack because it's built into some part of the default configuration.

But when I try to deploy it, I get "Application install on simulator failed. Bundle path does not exist."

I have no idea how to fix that one.

You might be interested in https://wiki.qt.io/Qt_for_OpenHarmony(portal)