[NgapWei]

As the title mentioned, today when I try to upload an apk to the google play store, I find out an error occur, because the apk only support 32bits machine, it is builded by armv7a compiler, Qt5.12.3.

 

The main reason I want to upload the app to the play store is avoid the permission issues, when I try to play the video by gstreamer, the adb always give me error message

 

W RenderThread: type=1400 audit(0.0:1201381): avc: denied { read } for name="perf_ioctl" dev="proc" ino=4026533700 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:proc:s0 tclass=file permissive=0

 

However, it works perfectly well with voice recording and playing audio,  I already add following permission into the manifest files and make sure they are checked when the app start.

 

<uses-permission android:name=”android.permission.RECORD_AUDIO”/>
<uses-permission android:name=”android.permission.READ_EXTERNAL_STORAGE”/>

 

Any suggestions except of root my machine?Thanks

[NgapWei]

Found Qt version with armv8a, guess this one is for 64bits

[NgapWei]

Find out this do not solve the issue, Google want us to package 32bits and 64bits binary together, anyway to do that with QtCreator/qmake?

This mean if I am using c++, I have to compile them as .so for different architectures?What a pain

[NgapWei]

Find out I can upload 3 apk to the stores, my question is, do I need to update my licenseKey version for each apk?

Tried to change the versionCode of AndroidManifest, but this do not work

[AlexFelgo Team]

Hi,

we covered all infos about Android 64-bit in this blog post: https://felgo.com/blog/android-64-bit-support-felgo-qt-cloud-builds

Cheers,
Alex

[NgapWei]

Thanks, my app use a lot of native codes to write qml extensions(it rely on gstreamer), don’t think cloud-builds can help me solve the issue

[AlexFelgo Team]

Hi,

the post also includes infos on local deployment, at “1. Build your Android App with 64-Bit manually using Qt Creator”. As every APK uploaded to a single release needs a uniqe version code, you will also need a new license key for each (as a key is bound to a version code). With the code example provided in the blog post, you can control that from your *.pro file and do not need to manually change the version codes in your manifest file or paste new license keys to the main file for every build.

Cheers,
Alex