Android app doesn't run

[mzimmers]

@JoeCFD well, as it turns out, it doesn't appear to be related to my changing the project name -- I had an old copy of the project, and that fails in the same way. (It had been awhile since I bothered trying to load to the tablet.)

I'm going to re-title this topic, as the current title is incorrect.

[ekkescorner]

@mzimmers what are your Qt and QtCreator versions ?
and Android target API ?

[mzimmers]

@ekkescorner
Qt 6.5.3
Creator 11.0.3

Not sure what an Android target API is - unless you mean arm64-v8a.

[ekkescorner]

@mzimmers arm64-v8a is the architecture - in this case arm 64bit
in QMake:
under Build Android APK Android Build Platform SDK is set to android-33 (Android 13), Android Build Tools are 33.0.2
and in .pro I have set Min SDK and target SDK:
ANDROID_MIN_SDK_VERSION = "23"
ANDROID_TARGET_SDK_VERSION = "33"
For me - working on macOS - I never have to install Gradle or so. it's working.
I always do 'Create Templates' as you have done. Sometimes I had problems creating templates and 'Replace all' - have done 'replace' for each file extra.
I'm using Qt 6.6 and QtC 11.0.2
Have no idea how this will be with CMake. Just fighting with my last 5.15 App-port to 6.6 (QMake), so soon will enter CMake ;-)

BTW: as @JoeCFD said: as packageName you should use your domain in reverse order together with a short app name, per ex. org.yourname.yourAppName and this must be unique. the packageName is independent from project name, per ex for a customer I'm building APKs with different packageNames like: de.theCustomer.theApp.test and de.theCustomer.theApp.prod while the project has a different name: theCustomer_theApp

[Shahab Khan]

This post is deleted!

[mzimmers]

Hi all -

I need to bump this, because I really need to get this app running on Android. I created a new, minimal project, and I'm still getting the error:

Error: Activity class {org.qtproject.example.minimal_map/org.qtproject.qt.android.bindings.QtActivity} does not exist.

I'm guessing it has something to do with my manifest file, and here's where I need help. I really don't understand most of the fields in this display:

So, a few questions:

1. the fields that look like: -- %%INSERT_APP_NAME%% --; am I supposed to replaceeverything with my own values, or do I keep the dashes and "%"?
2. do I need to replace all of those fields?
3. what exactly is an "activity name?" My searches haven't revealed much.

Thanks for any assistance...

[ekkescorner]

@mzimmers said in Android app doesn't run:

the fields that look like: -- %%INSERT_APP_NAME%% --; am I supposed to replaceeverything with my own values, or do I keep the dashes and "%"?
do I need to replace all of those fields?

if you don't replace the values, then QtCreator will fill this value. After building the project, you can go to the build dir, find the manifest and open to see what vaklues QtC inserted.
In my apps I always put my own value in, per ex. QtWS for the QtWorldSummit App.
if you change the value, switch editor to xml source to see that Application label (https://developer.android.com/guide/topics/manifest/application-element#label) and Activity label (https://developer.android.com/guide/topics/manifest/activity-element#label) changed.

what exactly is an "activity name?" My searches haven't revealed much.
see above. simply search for "android manifest doc"

[JKSH]

@mzimmers said in Android app doesn't run:

I created a new, minimal project, and I'm still getting the error:

Quick sanity check: Do you get the error if create a new, minimal project and run it on Android without doing anything at all to the manifest file? In other words, just create the project and build + run it.

I'm guessing it has something to do with my manifest file, and here's where I need help. I really don't understand most of the fields in this display:

Be warned, that manifest editor is badly broken: https://bugreports.qt.io/browse/QTCREATORBUG-27119 I recommend that you don't touch it -- even the act of opening that editor is enough to corrupt the manifest file in some cases.

[ekkescorner]

@JKSH said in Android app doesn't run:

Be warned, that manifest editor is badly broken: https://bugreports.qt.io/browse/QTCREATORBUG-27119 I recommend that you don't touch it -- even the act of opening that editor is enough to corrupt the manifest file in some cases.

also have noticed that opening with Manifest Editor sometimes changes the content. But in my cases it was only a reformatting / reordering and nothing destroyed. (QtC 12.0.1)

BTW: I'm getting best experiences this way:

• Update Templates
• check changes (using git)
• add / replace with my settings
  this way I'm always getting the newest recommended values

[mzimmers]

@ekkescorner said in Android app doesn't run:

check changes (using git)

Could you elaborate on this? Changes to what, exactly?

[ekkescorner]

@mzimmers see here what I did while updating from 5.15 to 6.6:
https://t1p.de/ekkeAndroidTemplates66
this will give you the idea how I'm doing this

[mzimmers]

@JKSH thanks for the warning about the manifest editor -- it looks like TQC has painted itself into a corner on this one.

I was going to try your suggestion, but now I have a different problem: my Android device shows as "disconnected" and I can't figure out what to do about this.

[mzimmers]

@ekkescorner that's a great page. I'm using 6.5.3; do you think your suggestions will work with this version?

[ekkescorner]

@mzimmers will be similar, but not the same. per ex. the Qt FileProvider only exists in 6.6+

[ekkescorner]

@mzimmers said in Android app doesn't run:

my Android device shows as "disconnected"

connected via wifi or via usb cable ?

[JoeCFD]

@mzimmers Click Manage Kits->Devices
select your device in Device combobox since your device may not be the default one.
Then click Debug above Run button and select your connected device.

[mzimmers]

@ekkescorner USB cable. I deleted that device, and am trying to create a new one, but it keeps trying to make an emulator, not a "real" Android device.

[ekkescorner]

@mzimmers creating devices is for emulators. to connect via USB see https://t1p.de/ekkeManageDevices

[mzimmers]

@JoeCFD interesting -- I thought I had deleted that device, but it still shows up (and appears to be selected):

I'm not sure what you are referring to with "Debug above Run button." I'm only trying to build a release version.

[mzimmers]

@ekkescorner oh, OK. I didn't realize that.

So...any idea why my device is showing as disconnected?