Android app doesn't run

[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

[mzimmers]

@JoeCFD
nobody home when I have JDK11 selected:

[JKSH]

@mzimmers said in Android app doesn't run:

Do I need to dig up an earlier version of the SDK now?

That's a bit tricky:

• The Latest version of the SDK Command-Line tools (v11+) requires JDK 17 now. In contrast, v10 of the Tools can work with JDK 11.
• Qt Creator expects you to use the SDK Manager to install the "Latest" version of the tools. So if you've upgrade those tools, you're expected to use JDK 17 too.

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

Hmm... that's weird. Sorry, I don't know if it's related to JDK 17 or not. (I haven't upgraded so I'm still using JDK 11 + SDK Command-Line Tools v10)

[mzimmers]

This post is deleted!

[mzimmers]

Using Android Studio's SDK Manager, I was able to install Android 13.0 (Tiramisu), and command-line tools 10:

and now my Android settings in Creator are totally whack:

I'm going around in circles here. Any ideas are appreciated.

[JoeCFD]

@mzimmers the SDKs from Android SDK Manager are not in your kit yet. Click SDK Manager button to add them.

[mzimmers]

@JoeCFD it doesn't work - there's nothing in the package window to add when I've selected JDK 11.

[ekkescorner]

@mzimmers I'm using JDK 17 for Qt 5.15.15 and 6.6

[JoeCFD]

@mzimmers I am running Qt 6.6.1 on Linux with qtcreator 11.0.3 and do not have any issue with the settings.

SDK path is not writable?

[mzimmers]

@JoeCFD I'm running on Windows 11. According to the properties of my Sdk folder, it was partially read-only, but I changed that, and it didn't help.

When I try to run the SCK manager, I get this error:

[JoeCFD]

@mzimmers

The error message indicates that you are trying to run a Java class file compiled with a higher version of the Java compiler than the version of the Java Runtime Environment (JRE) you have installed.

In this case:

Class file version 61.0 corresponds to Java 17.
Class file version 55.0 corresponds to Java 11.

==============================================================
Your installation is messed up.