I had a Progaurd file for release. Removing that fixed the problem: keepattributes LineNumberTable,SourceFile renamesourcefileattribute SourceFile

@MrPotato On the arch wiki I'm told to build: android-armv7a-eabi-qt5AUR - armeabi-v7a android-aarch64-qt5AUR - aarch64 android-x86-qt5AUR - x86 android-x86-64-qt5AUR - x86_64 from the AUR. But apparently the packages have been dropped. From the maintainer: I'll drop this package, I been thinking and there are a lot of strong reasons not to waste any time maintaining it. KDE doesn't provide an easy way to download the entire Qt source code in a single package, like in the official Qt releases. Also, KDE doesn't provides tagged versions, I've to keep tracking manually the latest commits, or converting it to a git package. It will require to split this package into 47x4 packages, 47 Qt modules and 4 architectures to maintain, that's 188 packages to maintain, absurd! Cloning a git repository is slower than just downloading a source package file, making the build even much slower and painful. Is a lot of work for something that will be dead in 1 year or 2 at most. Good luck to the one that will step up to take care of this monstrosity, to the rest of developers, don't be lazy and consider switching to Qt6. Which leaves me with the only alternative being to use the Qt Online Installer. I guess this must be the only option. Which is a bummer, because now I'll have duplicate packages on my system.

@Fitndex-developer said in In-App Purchasing of Registered Product (google store): com.fitndex.theApp Hello Everyone, since there has been no activity on this post, I thought I'd let everyone know that this setup works with one change in the code: do not include the app name in the identifier. identifier: 30day_data_access ... is correct identifier com.fitndex.theApp.30day_data_access ... is wrong On google play I was missing the following. I was in internal testing and the app had not been published, i published to closed testing. Add licence testers to the app in google play console (this is different than the release track email list) If using the same app version code as the published version, testing will work, even when plugged in for debug, if you are logged into the tester gmail account. I took a crack at developing subscriptions in java, and for me, that is going to take a while but I will finish (the jni messenger example in android extras helps start with communicating with java if you are new to that), Qt purchasing makes life a lot easier just most of your work is going to be on the google play console side when dealing with Qt Purchasing. So if things are not working, check your settings with google (or apple), that is most likely it. Qt purchasing does not handle subscriptions, it will never find your subscriptions no matter what. The reason for that is the developers could not come up with a platform independent solution for subscriptions. The community needs to figure this one out for everyone. An example anyone? Since monetization is so important; and documentation/examples on qt purchasing are minimal, I hope this helps some of you!! I could have used something like this when I was working on it. FITNDEX HOME now we are on track to launch this summer. You can join the beta on website. Lets help each other get to market. The more money we all make, the better Qt will get, I promise. Steve

Guys; May you please some help. I reached to a dead end

Never mind. I had to set the surface format version to 3.0 in main, at the top. int main(int argc, char *argv[]) { QSurfaceFormat f; f.setVersion(3,0); QGuiApplication app(argc, argv); //... }

Modern Androids heavily restrict access to the file system, and getting file URLs is no longer allowed. I suspect you have bumped target SDK when upgrading and now you are bound by newer rules from Android: you'll have to upgrade your code to use storage providers and permissions. Some info: https://developer.android.com/training/data-storage and https://developer.android.com/guide/topics/providers/document-provider

@dev_liya Why do you need threads to generate random numbers?! You can do this way easier using QTimer...

I have found a solution! I did multiple things: Used newer template files for Android from Qt/6.2.3/android_arm64_v8a/src/android/templates/ (res/values/libs.xml - overwritten, build.gradle - overwritten, AndroidManifest.xml - copy and paste and then edited the content and added the missing things from my old one) Used newer gradle files from /Qt/6.2.3/android_arm64_v8a/src/3rdparty/gradle/gradle/wrapper/ - overwritten Upgrade of Qt Creator, Qt 6.2.2 -> 6.2.3, Android SDK, Android NDK My current Manifest: <?xml version="1.0"?> <manifest xmlns:android="http://schemas.android.com/apk/res/android" package="org.dontpanic" android:installLocation="auto" android:versionCode="20000" android:versionName="2.0"> <uses-sdk android:minSdkVersion="23" android:targetSdkVersion="31"/> <!-- The comment below will be replaced with dependencies permissions upon deployment. Remove the comment if you do not require these default permissions. --> <!-- %%INSERT_PERMISSIONS --> <!-- The comment below will be replaced with dependencies permissions upon deployment. Remove the comment if you do not require these default features. --> <!-- %%INSERT_FEATURES --> <supports-screens android:anyDensity="true" android:largeScreens="true" android:normalScreens="true" android:smallScreens="true" /> <application android:name="org.qtproject.qt.android.bindings.QtApplication" android:extractNativeLibs="true" android:hardwareAccelerated="true" android:label="@string/app_name" android:icon="@drawable/icon" android:requestLegacyExternalStorage="true"> <activity android:name="org.qtproject.qt.android.bindings.QtActivity" android:configChanges="orientation|uiMode|screenLayout|screenSize|smallestScreenSize|layoutDirection|locale|fontScale|keyboard|keyboardHidden|navigation|mcc|mnc|density" android:label="@string/app_name" android:launchMode="singleTop" android:screenOrientation="portrait"> <intent-filter> <action android:name="android.intent.action.MAIN"/> <category android:name="android.intent.category.LAUNCHER"/> </intent-filter> <!-- Application arguments --> <meta-data android:name="android.app.arguments" android:value="-- %%INSERT_APP_ARGUMENTS%% --" /> <!-- Application arguments --> <meta-data android:name="android.app.lib_name" android:value="-- %%INSERT_APP_LIB_NAME%% --" /> <!-- Background running --> <!-- Warning: changing this value to true may cause unexpected crashes if the application still try to draw after "applicationStateChanged(Qt::ApplicationSuspended)" signal is sent! --> <meta-data android:name="android.app.background_running" android:value="false" /> <!-- Background running --> <!-- extract android style --> <!-- available android:values : * default - In most cases this will be the same as "full", but it can also be * something else if needed, e.g., for compatibility reasons * full - useful QWidget & Quick Controls 1 apps * minimal - useful for Quick Controls 2 apps, it is much faster than "full" * none - useful for apps that don't use any of the above Qt modules --> <meta-data android:name="android.app.extract_android_style" android:value="minimal" /> <!-- extract android style --> </activity> <service android:name="org.dontpanic.NotificationService"> <meta-data android:name="android.app.lib_name" android:value="-- %%INSERT_APP_LIB_NAME%% --"/> </service> <receiver android:name="org.dontpanic.NotificationReceiver" android:enabled="true" android:exported="true"/> <receiver android:name="org.dontpanic.RebootReceiver" android:enabled="true" android:exported="true"> <intent-filter> <action android:name="android.intent.action.BOOT"/> <action android:name="android.intent.action.LOCKED_BOOT_COMPLETED"/> <action android:name="android.intent.action.BOOT_COMPLETED"/> <action android:name="android.intent.action.QUICKBOOT_POWERON"/> <action android:name="android.intent.action.REBOOT"/> <action android:name="com.htc.intent.action.QUICKBOOT_POWERON"/> <action android:name="android.intent.action.USER_PRESENT"/> <category android:name="android.intent.category.DEFAULT"/> </intent-filter> </receiver> </application> <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/> <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/> <uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED"/> </manifest>

I have the same problem :-1: error: Cannot find application binary in build dir .../build-ICS_MedicalDemo-Android_Qt_5_15_13_Clang_Multi_Abi-Debug/android-build//libs/x86_64/libICS_MedicalDemo_x86_64.so. What could be the issue in this case ? I have already set ANDROID_ABI to correct x86_64 setting. 

My question is I want to send data and retrieve it in java. for exeomple void ActivityHandler::activityReceiver(int requestCode, int resultCode, const QAndroidJniObject &data) { if (requestCode == REQUEST_CODE) { if (resultCode == RESULT_OK) { const QAndroidJniObject key = QAndroidJniObject::fromString("message"); const QAndroidJniObject message = data.callObjectMethod( "getData", "(Ljava/lang/String;)Ljava/lang/String;", key.object()); if (message.isValid()) emit ActivityHandler::instance()->receiveFromActivityResult(message.toString()); } else { emit ActivityHandler::instance()->receiveFromActivityResult("Rejected!"); } } }

@Dmitriano Probably I had some wrong build configuration, after some experimentation and switching to Java11 it become about 1MB.

@Dmitriano ANDROID_PLATFORM is correct with NDK 21.3.6528147 and NDK 22.1.7171670 but with NDK 23.1.7779620 it is not.

@Dmitriano Sorry, have you the script to compile 5.15? Thanks