Android APK realease includes all platforms?



  • For Android development, on QT Creator appears the option to compile to x86 or armeabi-v7a architecture. After compile to armeabi-v7a, I've uploaded the APK generated to Google Play Developer Console. On the Developer Console, appears that the APK has these native platforms: arm64-v8a, armeabi, armeabi-v7a, mips, mips64, x86, x86_64. Are all supported?

    If the response is yes, what about the x86 compile option?

    If the response is no, is it a bug?


  • Lifetime Qt Champion

    Hi,

    That's a bit surprising, mips is clearly not an architecture provided.

    Might be a silly question but are you sure that it's not talking about the architecture you can provide rather than the one in the APK.



  • I think that it's what APK supports because this information appears when I clik on the APK uploaded and the title is "APK DETAILS".

    To test it, I've created another APK compiled with the x86 architecture (the previous is compiled with armeabi-v7a). After uploading to Google Developer Console, appears this error:

    This configuration cannot be published for the following reason(s):
        Version 106 is not served to any device configuration: all devices that might receive version 106 would receive version 107.
    

    This error appears because both, 106 and 107 version support all architectures.



  • I've found it!

    I'm using the library Crashlytics and when generates the APK the library is included for all architectures (this library has versions for all architectures). If compile for armeabi-v7a, all the libraries are include on the armeabi-v7a, but appears directories for all the other architecutes and inside it only appears this library, so, the Developer Console thinks that all architectures are supported.


  • Lifetime Qt Champion

    Glad you found out and thanks for sharing !

    Since everything is cleared now, please mark the thread as solved using the "Topic Tools" button so that other forum users may know a solution has been found :)


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.