Before I had the support-screens directive, then I have changed to compatible screens, and I think the problem started there. Before I also had the required min dpi attribute on support-screens and now I have completely removed it. So, I ended with this only:
<supports-screens android:smallScreens="false" android:normalScreens="true" android:largeScreens="true" android:xlargeScreens="true”/> Nuno Santos Founder / CEO / CTO www.imaginando.pt +351 91 621 69 62 > On 30 Jul 2015, at 10:13, Daniel França <daniel.fra...@gmail.com> wrote: > > Hi Nuno, > Sorry, I didn't get what you changed to make it work. > Could you explain? > > Em qui, 30 de jul de 2015 às 10:58, Nuno Santos <nunosan...@imaginando.pt > <mailto:nunosan...@imaginando.pt>> escreveu: > Harri, > > Yesterday, I have finally managed to solve the problem with the help of a > user. > > One of the biggest issues was the misleading information provided by Google > Play Developer support about the unsupported platforms. > > The problem was actually derived from the support-screens. My last try was: > > <supports-screens android:smallScreens="false" android:normalScreens="true" > android:largeScreens="true" android:xlargeScreens="true”/> > > And it is now working for both apps. > > No problems with Qt, Android-SDK, Android-NDK or so ever. > > I’m glad this is solved as a lot of users couldn’t install from the store. > > Thanks for your feedback. > > Nuno > >> On 30 Jul 2015, at 09:51, Harri Pasanen <ha...@mpaja.com >> <mailto:ha...@mpaja.com>> wrote: >> >> >> 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 >> >> _______________________________________________ >> Interest mailing list >> Interest@qt-project.org <mailto:Interest@qt-project.org> >> http://lists.qt-project.org/mailman/listinfo/interest >> <http://lists.qt-project.org/mailman/listinfo/interest> > > _______________________________________________ > Interest mailing list > Interest@qt-project.org <mailto:Interest@qt-project.org> > http://lists.qt-project.org/mailman/listinfo/interest > <http://lists.qt-project.org/mailman/listinfo/interest>
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
