I have the targetSdkVersion set as 17 in my manifest. Kindly let me know if there will be any problem when I run this in the phone which has the API of 18.
Manifest xml :
<uses-sdk
android:minSdkVersion="8"
android:targetSdkVersion="17" />
I will not support API 18 and if you upload it to play store
then it will not be visible for all device > API 17
For example my Application which is uploaded to Play Store have 10 - 18 API support
so it support 3326 Type of devices on play store similarly and it is available for those api level devices only
My app on PlayStore
Permissions also matters
Say if you want Wifi Permissions and device not have wifi it won't be visible for those device who don't have wifi
If you directly install it to Device > API 17 it will give warning but will install
The Official Documentation Mentions here
From the official documentation (link):
To maintain your application along with each Android release, you should increase the value of this attribute to match the latest API level, then thoroughly test your application on the corresponding platform version.
No. But it is recommended to set android:targetSdkVersion to the newest version.
Related
I have an Wear OS app on the Play Store. Recently I wanted to upload update but I'm getting error Your app currently targets API level 30 and must target at least API level 31 to ensure that it is built on the latest APIs optimised for security and performance. Change your app's target API level to at least 31.
I would understand this for regular phone app but in Play Console Help Center they clearly state that Wear OS app are excluded (since nothing newer than API 30 exists there anyway) - https://support.google.com/googleplay/android-developer/answer/11926878
This is the error:
I'm not sure how they define (distinguish) between regular app and Wear OS app because when I've created store listing it was basically regular app setup + enabling Wear OS form factor but all the documentation describe it this way. And the distribution was working fine so I consider my app listing Wear OS only.
I also have <uses-feature android:name="android.hardware.type.watch" /> in the manifest as required.
Tldr; is it something I'm missing in my setup to be eligible for this target API exception for Wear OS or is this console error happening to others as well?
Change Your targetSdkVersion to 31
then try to Upload on Play Consol
Understand Google Play has a new API requirement:
Google Play will require that new apps target at least Android 8.0
(API level 26) from August 1, 2018, and that app updates target
Android 8.0 from November 1, 2018.
Previously I uploaded an APK that was has the following values:
Afterwards I made an updated before November 2018:
I plan to do an update soon and would like to ensure I am meeting all requirements beforehand.
Does it mean I have fulfilled the new API requirement? Should I be looking at API levels or Target SDK? Is API levels referring to the minimum API level?
You could check your android manifest for the following lines:
<uses-sdk android:minSdkVersion="16" android:targetSdkVersion="26" />
As long as the target is 26 and above, I believe it should work fine.
I have published an apk recently using this without any issues.
You may refer to: The problem about Google Play's target API level requirement , in which someone has explained the min and target version.
Received below warning from PlayStore, What does it means?
Users with version 15 of the APK (targeting 22 version of the SDK or earlier) will perform the update. However, once the update is complete, they will no longer install APK targeting 22 version of the SDK or earlier.
Trick
If this change is desired, make sure that users doing in the future to update this APK to spend 23 or later.
Old Version details :
android:minSdkVersion="18"
android:targetSdkVersion="19"
android:compileSdkVersion="21"
Latest version details :
android:minSdkVersion="18"
android:targetSdkVersion="25"
android:compileSdkVersion="25"
Targeting API 23 or later means you must request dangerous permissions at runtime. The warning is staying that this is a one way switch: there is no way to revert back to targeting API 22 or earlier once you make the switch to the runtime permission model. The Dev Console is just confirming that you do indeed want to make the permanent switch.
Getting warning while uploading any apk on Play Store.
You uploaded an APK that uses Google Play services version 4452000.
This will only work with Android API levels of 9 and above. It is
discouraged to use this Google Play services version unless you have
set the minSdkVersion in your manifest to 9 or higher
What is the actually problem here?
This version of Google Play services that you use in your app is compatible with android device that runs android 2.3(API level 9) or higher. if you want support android 2.2(API level 8), install Google Play services for Froyo from SDK manager and use that version in your project. you can set minSdkVersion to 9 if you want to use current Google Play services that you have.
Yes actual problem is with minSdkVersion
you might have used
<uses-sdk android:minSdkVersion="8"/>
change it to
<uses-sdk android:minSdkVersion="9"/>
you could try this code.
<uses-sdk android:minSdkVersion="9" android:targetSdkVersion="16"/>
There is a line in the AndroidManifest.xml
android:minSdkVersion="10" android:targetSdkVersion="19"
Does it mean that if I include minimum and maximum SDK version in the AndroidManifest.xml file and build the APK using phonegap/cordova CLI (Command Line Inteface),
than a SINGLE APK file generated can be installed on ALL Android Devices ranging from Android 2.3.4 to Android 4.4
I have read posts that developing using Android SDK(native APP) it enables the APP to work on the range of devices.
Is it true for PhoneGap/Cordova generated APK file as well? (Note: I am not planning to use Google Play services for distributing the APP.)
Do we need to generate APK file for each SDK version?
The implications of these two variables is the same for both native apps and PhoneGap/Cordova apps.
minSdkVersion will set the minimum version of Android required to run your application. If a user is running any version below this, they will not be able to install your application (regardless of whether or not you are distributing via the Play Store).
targetSdkVersion specifies the latest version of Android that you have tested for. It will not change who can install your app, but it will change the behavior of your application. For example, if this is less than 14, you won't have an action bar. If it is less than 19, then users running KitKat and above will not see your content in a Chrome-backed WebView (it will be the older WebView implementation).
Generally you just set targetSdkVersion to the latest available version of Android.
Do we need to generate APK file for each SDK version?
No. You need one APK with mindSdkVersion set to the minimum version you support and targetSdkVersion to the latest version of Android you have tested against.
You can specify a maxSdkVersion, which will actually limit the maximum version you support, but you generally should not do this unless you have a good reason to.
android:minSdkVersion is the minimum API level that device needs for run your app.
android:targetSdkVersion is the latest tested API that works with your app, and you should set there the latest API version.
Following useful data about the number of devices running API versions: https://developer.android.com/about/dashboards/index.html?utm_source=ausdroid.net