Qt Android 32 and 64 bit version package error
-
wrote on 4 Jul 2020, 12:59 last edited by
I have application in Google play, compiling on Qt 5.12 32 bit. When I try upload new version application, compiled on Qt 5.15 I get error:
**Your APK or Android App Bundle needs to have the package name *:
You need to use a different version code for your APK or Android App Bundle because you alreadv have one with version nada 1 -
I have application in Google play, compiling on Qt 5.12 32 bit. When I try upload new version application, compiled on Qt 5.15 I get error:
**Your APK or Android App Bundle needs to have the package name *:
You need to use a different version code for your APK or Android App Bundle because you alreadv have one with version nada 1wrote on 4 Jul 2020, 14:19 last edited by@Vitaliy
the version codes of the 32-bit and 64-bit apks should be consecutive, while the version name should be the same.
E.g: for my application, both have version name 2.8, but version code of 32-bit is 290, and version code of 64-bit is 291 -
take a llok at androids docs: https://developer.android.com/google/play/publishing/multiple-apks
-
wrote on 5 Jul 2020, 16:31 last edited by
Thanks for answers. Qt 5.15 does not have separate compilation of 32 and 64 bit android applications. Instead, should the aab format include 32 and 64 bit variant application?
-
see here: https://www.kdab.com/qt-for-android-better-than-ever-before/
you can build aab's or apk -
wrote on 6 Jul 2020, 13:59 last edited by
Ok, Thanks!
-
wrote on 6 Jul 2020, 15:23 last edited by
This part seems pretty clear:
You need to use a different version code ...
Therefore, I assume the confusion stems from why the AAB is out of compliance?
Have you unpacked the AAB to see what is inside? That seems worthwhile. If you unpack the AAB and locate version information inside of it, perhaps this will provide insight into what Qt chose to populate for you. (Here is a post on stackoverflow about unzipping an AAB).
So far, I have only uploaded to Google play using "fat APK" (APK file with multiple cross-platform binaries), so I certainly am not an expert.
I have this section in my
pro
file, following the advice from Qt online docs:android { DISTFILES += \ $$top_srcdir/src/lib/android/AndroidManifest.xml ANDROID_PACKAGE_SOURCE_DIR = $$top_srcdir/src/lib/android }
And every time I upload a new fat APK, I edit the manifest before building the new release. Edits like so:
diff --git a/src/lib/android/AndroidManifest.xml b/src/lib/android/AndroidManifest.xml index c83c9cc..8b72b2e 100644 --- a/src/lib/android/AndroidManifest.xml +++ b/src/lib/android/AndroidManifest.xml @@ -3,8 +3,8 @@ <!-- versionCode must be an ever-increasing integer used by play store --> <manifest package="org.anon.myapp" xmlns:android="http://schemas.android.com/apk/res/android" - android:versionName="2020-Jun-23" - android:versionCode="1" + android:versionName="2020-Jun-30" + android:versionCode="2" android:installLocation="auto"> <uses-permission android:name="android.permission.INTERNET" /> <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
1/7