The process "...\android_armv7\bin\androiddeployqt.exe" exited with code 14.

J.Hilk · 23 Apr 2019, 11:14

@tomy I would uninstall all preview packages. That was cause for a similar issue from on other poster recently.

Can't quite find the post.
"The search function is not the best" ...

tomy · 23 Apr 2019, 11:16

@J.Hilk

I removed all packages with the word "preview" in SDK:

Yet, the same errors!

J.Hilk · 23 Apr 2019, 11:30

@tomy
just to make sure, you did a complete rebuild after the removal ?
deleted building dir, rerun qmake.. the usual ?

tomy · J J.Hilk 23 Apr 2019, 11:16

@J.Hilk

WOW Hilk! :) :)
I did these and re-built the project. This time it built the APK and prior errors became vanished except for few normal warnings! :)

Thanks so much for your help. Vielen Dank. :)

tomy · 23 Apr 2019, 15:15

@J.Hilk

I'm using 18b and that one is working fine for me, haven't updated in a while.

Do you mean that when some version of NDK, like 18b, is working properly for apps for the time being, we shouldn't replace it with some newer version even if a newer version of Android is published and installed on Android devices?

I mean, can it support future versions of Android and will work properly on devices running those new versions too?

And about JDK, what version do you suggest to be good for recent and probably prior versions of Android, please?
As you know, the current version of Android is 9, I suppose.

J.Hilk · 23 Apr 2019, 16:40

@tomy

well
that's a bit complicated.
For a long time Qt was limited to a specific ndk, as some old stuff was dropped, that Qt relied on.

With 5.12 and onwards it should now be "latest version of ndk" according to the docu.
That, apparently, does not include the preview/release candidates.

In the end you're limited to what google permits on the play store and that is, IIRC, currently the sdk platform 27 which is Android 7 !?
That means if you want to upload a new app or update an old one your Target SDK should be 27 or newer.

I personally think, If it ain't broke, don't fix it ;-)

I'm running jdk1.8.0_192 and I'm not updating, if I don't have to.

tomy · 23 Apr 2019, 19:01

@J.Hilk, thanks.

With 5.12 and onwards it should now be "latest version of ndk" according to the docu.
That, apparently, does not include the preview/release candidates.

I didn't understand the part "the preview/release candidates" for ndk!

If we want to use the latest "stable" version of ndk, so the choice will be android-ndk-r19c-windows-x86_64.zip, but you're seemingly using this r18b android-ndk-r18b-windows-x86_64.zip. (For Window x64 for instance).
So the question is why do you use r18b while Docs says you need to use r19c, please?

In the end you're limited to what google permits on the play store and that is, IIRC, currently the sdk platform 27 which is Android 7 !?

Apparenlty the latest version is Pie 9 API level 28.

That means if you want to upload a new app or update an old one your Target SDK should be 27 or newer.

My android build sdk (for any QML app for Android) is always on android-28.
Bad habit?

I personally think, If it ain't broke, don't fix it ;-)

I didn't get this part either! :) What "it" do you say please?

I'm running jdk1.8.0_192 and I'm not updating, if I don't have to.

The question is, when do you think/feel you have to update it?
I want to copy that habit. When should I know it's time to update sdk, jdk, or ndk generally? Does it depend upon the version of Qt or android published or some other thing/item?

J.Hilk · 23 Apr 2019, 19:15

@tomy

I didn't understand the part "the preview/release candidates" for ndk!

Google, like other software companies, have official releases of their software and release candidates or preview versions of upcoming software.
Basically open Beta access to flush out bugs/incompatibilities or testing of new features/apis

Using one of those beta versions is bound to have bugs in them, making them not a viable candidate for development, but rather a test/check if your software is still working as indented in the upcoming releases.

So the question is why do you use r18b while Docs says you need to use r19c, please?

When I setup qt for android 5.12.0, 18b was the latest official release, and even listed in the docu as such.

Apparenlty the latest version is Pie 9 API level 28.

yes, but I was talking about the oldest api level still allowed to be used in the PlayStore.

My android build sdk (for any QML app for Android) is always on android-28.
Bad habit?

No, not necessarily, at least in my opinion. Use what works ;-)

I didn't get this part either! :) What "it" do you say please?

https://www.urbandictionary.com/define.php?term=if it ain't broke%2C don't fix it

The question is, when do you think/feel you have to update it?

when something doesn't work anymore with old apis/software.
Google is going to require 64bit apks alongside normal ones very soon, as in this or the coming year.
I'm sure an update on my side is being required than, at the very least.

tomy · 23 Apr 2019, 20:06

@J.Hilk

The phrase was a bit old school. ;-) hhhhh

Anyway, I mean the word you were referring by 'it' more. I suppsoe it was "sdk api level".

I installed 5.12.3 and it's given me both MinGW 32-bit and 64-bit! Not the thing you were waiting for?

To sum up, there is no version of ndk and jdk which will work for any devices running Android from 4 to 9, right? And do we just need to test?! (I don't think so!)

And being up-to-date for all stuff (sdk, ndk and jdk) doesn't guarranty that your Android app works on all various devices. Right?

J.Hilk · 23 Apr 2019, 20:16

@tomy

I installed 5.12.3 and it's given me both MinGW 32-bit and 64-bit! Not the thing you were waiting for?

No I actually mean this one.

To sum up, there is no version of ndk and jdk which will work for any devices running Android from 4 to 9, right? And do we just need to test?! (I don't think so!)

Well, Qt is limited to minimal Android version of 4.4. And any APK that works on the newest api should also work backwards without (much) issues. That one google actually get's down pretty good.

And being up-to-date for all stuff (sdk, ndk and jdk) doesn't guarranty that your Android app works on all various devices. Right?

I would say, mostly correct ;-)
nothing is guaranteed.

tomy · 23 Apr 2019, 20:43

@J.Hilk

No I actually mean this one.

Well, Qt is limited to minimal Android version of 4.4. And any APK that works on the newest api should also work backwards without (much) issues.

But the sdk for that level should have been previously installed, yeah?

I would say, mostly correct ;-)
nothing is guaranteed.

Thanks.

J.Hilk · 23 Apr 2019, 20:51

@tomy said in The process "...\android_armv7\bin\androiddeployqt.exe" exited with code 14.:

But the sdk for that level should have been previously installed, yeah?

nope that‘s just waste of hd-space, gradle will only ever use one version anyway. By default the latest, I think.

tomy · 23 Apr 2019, 20:59

@J.Hilk

nope that‘s just waste of hd-space, gradle will only ever use one version anyway. By default the latest, I think.

Really?

Do you mean the part inside the red line in the screenshot below is enough for almost any Android device?

J.Hilk · T tomy 23 Apr 2019, 20:51

@tomy jupp
this is my install, I'm able to cover nearly everything, according to the PlayStore statistics: