Android Question This app was built for an older version of android...

[avalle]

Hi all,
I'm testing a small app with multiple devices and I get the following warning when launching the app on a Galaxy S10 with Android 10: "This app was built for an older version of android and may not work correctly. Try to check the availability of updates or contact the developer". (note: this translation is mine from the native OS language).
The app works as expected, but I would like to remove this warning before posting it to the PlayStore.

My application is rather simple, just sending a receiving messages via UDP. using android.permission.INTERNET due to UDPSocket.
Compiled with B4A 10.2 / Android SDK 30 / Java 8_172 64 bit
Libraries: Core 9.90 + Network 1.52

Here's the manifest I'm using:

AddManifestText(
<uses-sdk android:minSdkVersion="14" />
<supports-screens android:largeScreens="true"
    android:normalScreens="true"
    android:smallScreens="true"
    android:anyDensity="true"
    android:targetSdkVersion="29"/>)
SetApplicationAttribute(android:icon, "@drawable/icon")
SetApplicationAttribute(android:label, "$LABEL$")

Anything odd I'm missing or ignoring?
Thanks
Andrea

 

[agraham]

This is normal under Android 10 as your manifest targetSdkVersion is missing (in your case) or is less than 28. There should be a warning at the top of the logs pane in the IDE telling you this.

 

[MikeSW17]

I see

android:targetSdkVersion="29"/>)

in the manifest - Line #7

 

[avalle]

Indeed I'm using the recommended android:targetSdkVersion="29"

In addition I also tried with android:targetSdkVersion="30" as I'm using Android SDK 30, and B4A gives me the warning "The recommended value for android:targetSdkVersion is 29 or above (manifest editor). (warning #31)", which does not seem correct. Sounds like a B4A bug?

 

[mcqueccu]

Not a bug. Until further notice, its advised we stick to 29 for now

 

[avalle]

Looks like I solved by modifying the Manifest to this:

AddManifestText(
<uses-sdk android:minSdkVersion="14" />
<uses-sdk android:targetSdkVersion="29" />
<supports-screens android:largeScreens="true"
    android:normalScreens="true"
    android:smallScreens="true"
    android:anyDensity="true"/>)
SetApplicationAttribute(android:icon, "@drawable/icon")
SetApplicationAttribute(android:label, "$LABEL$")

I wonder what's the difference between setting targetSdkVersion as <uses-sdk> and <supports-screens>, which has worked for me so far prior to Android 10.

 

[agraham]

<supports-screens> has nothing to do with <uses-sdk>. Adding <uses-sdk android:targetSdkVersion="29" /> is what I would expect to fix it.

 

[MikeSW17]

<supports-screens> has nothing to do with <uses-sdk>. Adding <uses-sdk android:targetSdkVersion="29" /> is what I would expect to fix it.

The OP already has targetSdkVersion="29" set.

 

[agraham]

The OP already has targetSdkVersion="29" set.

It was in the wrong place under <supports-screens ...> and not <uses-sdk ...> and was being ignored.

 

[avalle]

That makes sense @agraham but I want to notice that the B4A IDE seems to consider it as valid, or at least the warning message is removed even with targetSdkVersion in the wrong place.

 

[agraham]

I don't think the IDE bothers to parse the manifest in any great depth. The default manifest puts everything in the right place. I don't know what you did to avoid that.

 

[avalle]

I started from an old project with the wrong string. Now I see that the IDE builds a default manifest if I clean it up.
I learned something new for me, thanks everyone for taking the time to answer my question.