Android app doesn't run

[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?

[JoeCFD]

@mzimmers click Devices and show the tabs. I am debugging my app for Android now and have debug build. If you are building release, then it is Release above Run button on the lower left corner of Qt Creator.

[mzimmers]

@JoeCFD

[JoeCFD]

@mzimmers is this device correct? Click the down arrow and you can see more.
If yes, check if the cable is on. I had this issue this morning. The cable was off.

[mzimmers]

@JoeCFD it's the same device that worked for me last year. And it's indeed connected (I think it would have to be if it's auto-detected).

[JoeCFD]

@mzimmers Go to your computer and click this device to see if you are able to browse inside this device. For example, copy a file from this device to your computer. If yes, this means the device is connected to your computer. Otherwise, it is not connected.

[mzimmers]

@JoeCFD tried that, and it sure appears to be connected:

I'm starting to wonder if there's something wrong with the SDK that Creator downloaded for me.

[JoeCFD]

@mzimmers yes, it is connected. Click the Android tab to see if anything is not set properly. I am now working with a Galaxy Tab A as well and do not have issues. Do you need to enable debugging in your Tablet? I remember you set it.

[mzimmers]

@JoeCFD bingo. Now my device shows as ready to use.

Unfortunately, I'm now back to my original error:

Activity Manager threw the error: Error type 3
Error: Activity class {org.qtproject.example.weatherinfo/org.qtproject.qt.android.bindings.QtActivity} does not exist.

And, to @JKSH's suggestion, this is without modifying any of the files in my android directory.

How do these settings compare with yours?

[JoeCFD]

@mzimmers I have JDK 11 and yours is 17. 17 is for Android 14. I do not think Galaxy has 14 now. Check the Android version in your tablet. Mine is 13.

[mzimmers]

@JoeCFD mine appears to be 11.

When I change my JDK to 11, I get the following errors:

Do I need to dig up an earlier version of the SDK now? The Android Studio download page seems to have only the latest versions.

[JoeCFD]

@mzimmers click SDK Manager button to install Android 13 SDKs