This release is not compliant with the Google Play 64-bit requirement problem
-
Hi,
I using ArcGIS_Runtime_SDK_Qt_Windows_100_14_01 sdk. Im using Qt Creator 7.0.2 Based on Qt 6.2.3 (MSVC 2019, 64 bit) and Kits Qt 5.15.2 (Android Clang Multi -Abi and MinGW 64-bit ) . I am uploading the new qt application (.aab file) to an old android application to google play console as an update.I get the error in the image below in the review and publish section:
Selected ABIs in Qt Creator:
here is also architectures property in "android-AppName-deployment-settings.json" file:
"architectures": {"arm64-v8a":"aarch64-linux-android", "armeabi-v7a":"arm-linux-androideabi", "x86":"i686-linux-android"}Maybe I came to the last stage to publish the apk, but I got an error, can you help?
-
Hi,
I using ArcGIS_Runtime_SDK_Qt_Windows_100_14_01 sdk. Im using Qt Creator 7.0.2 Based on Qt 6.2.3 (MSVC 2019, 64 bit) and Kits Qt 5.15.2 (Android Clang Multi -Abi and MinGW 64-bit ) . I am uploading the new qt application (.aab file) to an old android application to google play console as an update.I get the error in the image below in the review and publish section:
Selected ABIs in Qt Creator:
here is also architectures property in "android-AppName-deployment-settings.json" file:
"architectures": {"arm64-v8a":"aarch64-linux-android", "armeabi-v7a":"arm-linux-androideabi", "x86":"i686-linux-android"}Maybe I came to the last stage to publish the apk, but I got an error, can you help?
@tkoka said in This release is not compliant with the Google Play 64-bit requirement problem:
ArcGIS_Runtime_SDK_Qt_Windows_100_14_01
This does not sound like it would be for Android.
-
ArcGIS_Runtime_SDK_Qt_Windows_100_14_01 sdk.exe is the exe file that allows us to use libraries such as Esri.ArcGISRuntime 100.14 and Esri.ArcGIS Extras 1.1 in Android applications and is used when creating a new ArcGis project in new Qt. It is shown in the picture below.
I use "Android Qt 5.15.2 Clang Multi-Abi" to compile or run my project in Qt. I tested the generated apk on devices, if there was any windows library, the apk would explode.
Also, I opened my .aab file as rar. In one of the 3 architectures (for example, armeabi-v7a) in the lib folder, there are files such as libEsriCommonQt_armeabi-v7a.so, libArcGISRuntimePlugin_armeabi-v7a.so, libArcGISExtrasPlugin_armeabi-v7a.so.No Windows related library was found.
lib folder:
I want my product published, please help me.
-
Hi,
What happens if you upload with only the 64bit variants enabled ?
-
Hi,
I using ArcGIS_Runtime_SDK_Qt_Windows_100_14_01 sdk. Im using Qt Creator 7.0.2 Based on Qt 6.2.3 (MSVC 2019, 64 bit) and Kits Qt 5.15.2 (Android Clang Multi -Abi and MinGW 64-bit ) . I am uploading the new qt application (.aab file) to an old android application to google play console as an update.I get the error in the image below in the review and publish section:
Selected ABIs in Qt Creator:
here is also architectures property in "android-AppName-deployment-settings.json" file:
"architectures": {"arm64-v8a":"aarch64-linux-android", "armeabi-v7a":"arm-linux-androideabi", "x86":"i686-linux-android"}Maybe I came to the last stage to publish the apk, but I got an error, can you help?
-
@SGaist I tried only 64bit variants but I get the same error, nothing changed.
@J.Hilk I tried unchecking x86_64 and x86 as you said and ticking all of them, but the result did not change.
Probably needed ArcGIS libraries for architectures other than armv7.For example like compiling ArcGIS in 64 bit (arm64-v8a) but I don't know how to do this compilation in version 5.15.2. Can you help?
Here is my Android kit detay below:
Here is also C compiler options from Combobox are also below:
-
How does your project build if you don't have that library for all the architecture ?
-
In my project, when the compilation is complete, it generally creates 3 architectures ( armeabi-v7a, arm64-v8a and x86) without looking at the architectures that are ticked in the Bilding Settings ->ABIs in Qt. When I asked the "Runtime SDK for Qt Question" side in Esri community about this problem "You should only be able to target ARM architectures, not x86s." I got the answer.(I guess x86 architecture uses support the emulator .)
If we are not going to use x86 architecture in solving the problem, how can we prevent it from coming automatically?
Can we prevent the automatic creation of x86 architecture by making changes to the Qt files?