Newer versions of Android are able to read native libs directly from the apk without extracting them if they are stored uncompressed in the apk. This is done to save disk space on the device, and the new default during apk creation, but Qt 5.12 does not handle this. To compress native libs again add android:extractNativeLibs="true" in AndroidManifest.xml to the application tag.

You define your value as a string, which is where the result is collected. Don't want a string, fix the software.

I don't understand this well: From looking at the documentation, it seems that the QAndroidJniObject constructor and methods have to be attaching and detaching the current thread to and from the JVM, which isn't going to work in a JNI thread that's already attached to the JVM. Does this mean that, if I call C++ function(that uses QAndroidJniObject) from java JNI class, it is not going to work? Because as I understand, QAndroidJniObject is attaching and detaching the current thread to and from the JVM, and the JNI java object that is calling native functions, is already attached to the JVM. Please correct me if I am wrong.

@ashajg how to registerReceiver in c++?

Turns out, with an android target of 23 or older my approach is more than fine. But google decided to make it more complicated going forwards. As 23 is no longer viable version for updates. So, I read through the block post (multiple times), extracted everything I needed and managed to cram everything into one java file. also I get this warning: WARNING: Configuration 'compile' is obsolete and has been replaced with 'implementation' and 'api'. It will be removed at the end of 2018. For more information see: http://d.android.com/r/tools/update-dependency-configurations.html since it's now April 2019 I'm going to ignore that until it bites me in the back ;-) All in all I'm once again reminded why I'm not a fan of Java.... Thanks @VRonin and @ekkescorner , for helping me solve this, very much appreciated.

@Qjay said in QtAndroid local notifications , notifications poping up immediately: the notifications are popping up almost instantly ( despite me providing time for it ). you pass the time you want it to be triggered from now on. The API expects a time since EPOCH (as your comment in the code also states) which are the milliseconds from 1970/01/01 on. So in your JAVA code add new Date().getTime() milliseconds to your current timeout. So far i am able to get the notifications ( but not on Android O ) did you read this already? Alos chekc the Qt debugger console and/or LogCat for suspicious messages regarding notifications.

Hi, No it's not. Your application becomes a library loaded by Android's runtime which requires a small amount of Java but you are writing and using C++. You can access Android's Java functionalities through JNI if needed.

Hi @Geeva, @Geeva said in JSON with multi tasking: @JKSH Thanks for solving basic confusion. I have one more doubt also. Here, I have attached program for verification. I hope you can provide a proper solution You're welcome. I'm happy to teach you basics. However, verifying your program is too difficult to do on a forum. You need to do 2 things: Take C++ lessons Practice writing and debugging simple programs for your hardware

Hi and welcome to devnet, That version of QtJambi is not part of Qt. In fact QtJambi has been deprecated a long time ago and the version you are using is a community edition. You should ask the authors of it directly.

@benlau Thanks for answering my question!!! I could solve it :D

Thanks for the information. I tested on a Windows 7 virtual machine and it works. So I suppose you are right about a compatibility problem with Sierra. I'll contact the current dev team of QtJambi.

@Zakaria Thanks! Still working in 5.9.2.