Details
-
Bug
-
Resolution: Fixed
-
P2: Important
-
6.2.2
-
None
-
Running Qt Creator 6.0.1 on Ubuntu Linux (latest LTS release). Using CMake.
-
Android
-
67471d5db (dev), 4a46d75c1 (6.5), b0f810903 (6.6), b8c39d79d (tqtc/lts-6.2)
-
2023wk24FOQtforAndroid
Description
Please look at this documentation page:
https://doc.qt.io/qt-6/android-publishing-to-googleplay.html
For the "Publishing single ABI bundles" section, it tells us how we should set the `QT_ANDROID_VERSION_CODE` for CMake so we can target mutiple ABIs. Say if I set that variable to "03210", since I'm building for ARM v7 (32 Bit ARM) and .AAB file, it's putting the version code as "3210", not "03210". In the `AndroidManifest.xml`, I see the correct version code (with the leading zero). But when I uploaded the .AAB files to the Google Play console, they were missing that leading zero. If you also find the `output-metadata.json` file (somewhere in the build output tree), you'll see it has a "versionCode" entry, but with the (incorrect) missing-leading-zero.
I'm not sure if this is coming from Qt, or one of Google's/Android's tools. An alternative versioning code scheme should be mentioned in the docs if this can't be fixed.
I'm using an AndroidManifest.xml that's generated from Qt Creator, that has all of those `-- %% ...` lines in them for build generation.
