[Interest] How does Google Play validates Android binaries?

[Harri Pasanen]

On 29/07/2015 19:51, Nuno Santos wrote:
> Hi,
>
> I’m having a serious issue with Android deployment and this is 
> something recent. I’m starting to think that this was not happening on 
> previous versions of Qt. I’m currently using Qt 5.4.2 and when I 
> deploy to Google Play, on some devices the app is not compatible (the 
> pattern seems to be high resolution devices). On my app manifest min 
> SDK is 14 and target SDK is 21. I also have a support-screens 
> directive with the following:
>
> <supports-screens android:smallScreens="false" 
> android:normalScreens="true" android:largeScreens="true" 
> android:xlargeScreens="true"/>
>
> The most awkward issue here is that a couple of months ago, the same 
> app was available to the same device and now it isn’t. There are some 
> possibilities in my list:
>
> - Google Play bug
> - Android build tools incompatibility
> - Qt behaviour change on androiddeployqt
>
> However I’m completely in the dark. I’m tired of making experimental 
> builds and uploads with no positive results.
>
> Does any one knows how does Google Play analyses APK’s in order to 
> determine if they are OK or not?
>
> The only thing Google tells me is: "unsupported native platform: 
> armeabi, armeabi-v7a” However, APK’s were built for armeabi-v7a and 
> x86, with a superior version number for x86.
>
You should not have armeabi as supported if you are building for 
armeabi-v7a.
Where does that come from?

> The .apk works on development but isn’t allowed thru Google Play.
>
> Is anyone here experiencing the same problem?
>

I haven't built a new android version for a few months, but when I did I 
was using some snapshot of 5.5 dev.   Do you use ant or Gradle for the 
build?

Harri

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20150730/9c5b43ae/attachment.html>