Updated answer:
Here he goes
There is a solution
go to:
Your Directory \ Android-KFOR Windows \ Tools \ Templates \ Projects \ NewAndroidApplication \ Root
Open:
AndroidManifest.xml.ftl File
Edit:
default:
<uses-sdk android:minSdkVersion="${minApi}" android:targetSdkVersion="${targetApi}" />
Modified by:
<uses-sdk android:minSdkVersion="${minApi}" android:targetSdkVersion="${buildApi}" />
So the problem is here:
The attribute name ${targetApi} was specified in the ftl file, but we select the buildApi value in the project creation window.
${targetApi} or ${buildApi} default value is a higher version, which means that in your SDK tool it is API 15. So there is always 15 in the manifest.
If you tried to create a new project with a target API of less than 10 or more than 15, in the manifest it will be indicated as only 15.
Try the following:
Create a project with the target program API 8 and you will see that the manifest of the target will be only 15. (Before modifying the ftl file). But project.properties been updated correctly.
So, if you change ${targetApi} to ${buildApi} in Manifest.xml.ftl , the problem will be solved.
This is a possible mistake in the edition of 20 SDK tools. Even I updated the SDK tools, which were also not allowed in the recent edition.
Hope this can be helpful to someone who comes across this.
Old answer:
He shows me too. But in my case, I chose API 14, and it shows android:targetSdkVersion="15" in the manifest.
I suppose that some reason should be there ... 4.0 or 4.2, it assigns 4.1 in the manifest ... Or there might be an error with the Eclipse IDE. Why can't you update the new version of the Eclipse IDE and try it. This can only be a problem with the IDE.
You see that Right click-Properties is Android, Checked is the same that you selected at the beginning.
And also project.properties has the same version that you selected at the beginning.