Please note https://bugreports.qt.io/browse/QTBUG-76411, as Android 8 and later have quite a few new restrictions to background services.

@BINALECTRUM said in Android build and deploy. 64bit, Clang, new app store developer console rules [2018 & 2019]: Is Qt going more in embedded/car side and just slowly drops Android/mobile platform? In Roadmap 2018 there is nothing new about mobile platform. i heavily doubt that. I guess the reason is more because Qt runs more or less stable on Android. There are no bigger features which need to be implemented, mostly bug fixing. What is your move Qt team on new app store rules in developer console: minimal platform-26 in August 2018 and 64-bit apk in 2019? Some new changes in build and deploy area? i asked this at the beginning of the year, but unfortunately haven't received an answer.

I just didn't have an execute permission for NDK compiler. The message is gone now

@egg.nut I met the same question,how do you solve it?

@Sanders I finally resolved my issue. The problem was due to the Qt libraries. Indeed I was using the 5.6 version and to fix it I downgraded to the 5.5 version

me too facing same problem. is there any solutions.

Is your Android app an Java or C++ app?

I finally found my issue. My include path did not point to the great folder (the one containing the QObject header) To fix it I used the include path flag with the ndk-build command

this works. if you use jactivity.callObjectMethod instead of jactivity.callMethod it just crashes. QAndroidJniObject jactivity=QtAndroid::androidActivity(); if(jactivity.isValid()) jactivity.callMethod<void>("setVolumeControlStream","(I)V",3);

Hi, You should add which OS you are using, what version of the Android NDK and SDK you are trying to use.

Até onde sei, 100% é maneira de falar. Eu diria 99%, porque todo app precisa de um ponto de entrada em Java, nem que seja só pra chamar depois o C++.