I have an Android APP in Google Play which I have created and Launched when we had API 18. Now API 19 has come, I just need to make my APP to be visible for all devices which has the latest OS versions.
Kindly let me know what are all changes I need to make in the existing package.
Thanks in Advance
Unless you specified maxSdkVersion (which would be weird) your app will be visible for all API 19 users.
So, the answer is: no change needed
Related
I'm trying to add a dark theme to my app (which uses an Android web view) but whenever I call to check WebViewFeature.isFeatureSupported(WebViewFeature.FORCE_DARK) to see if my web view supports it, it returns false. I'm running on a simulator with API version 29, and my app has a target version of 29 with a min version of 16. How can I make sure this method returns true?
According to the accepted answer of Letting WebView on Android work with prefers-color-scheme: dark
The isFeatureSupported check is to make sure the Android System
WebView version the user has installed on their device supports dark
mode (since this can be updated or downgraded independently from the
Android version through Google Play)
So in my case, after I updated Android System Webview on the device/emulator, the issue was resolved. If you have problem to update the app (for example, update pending problem), please check whether the app has auto-update enabled. Check auto-update of app in Google Playstore. For more possible solutions to update problems, please refer to this article: Fix: Chrome and Android System Webview is not getting updated
My running environment:
minSdk 23
targetSdk 31
Pixel 3 API 29
Hope it helps!
I do not work with code at all. But we have 1 app on android programmed with React Native (old version).
Some told me that when Android Q (or 10) is published we need to upgrade our source code to be able to "publish" new apps or new updates to the stores.
This is true? If this is true, before what date we need to update our code for posting new updates or versions?
Thank you very much!
No. As of August, the Google Play Store required your targetSDKVersion to be at least 26, and I'm sure in a year or so they'll up it to 27. But nothing is needed just to support Android Q, unless your app is using a feature/API that got significantly changed.
I've downloaded the latest version of libGDX framework, which is meant for API level 20. Now, I'd like to target API level 19, since it's market share is HUGE, but the framework's developers "strongly discourage" using older versions. I could create the project using API level 20 SDK, then change the SDK when I import it to Android Studio, but I have no idea how it'll work out. Is it going to work, or I must use an older version to reach API level 20? (Maybe alternatives?)
The documentation wasn't too helpful, and I haven't seen anyone else having a problem like this, so I might have missed something.
Typically, you always want to target the most recent API version available, and set your minSdkVersion as low as you are willing to put the effort into supporting.
However, LibGDX is only officially tested up to level 20, so this is the safe target to use. You only need to go higher than 20 if there are some new API features you want to use. If you do that, make sure you test on a device with that API or later, since LibGDX hasn't officially started supporting it.
If you target 20, it will still work fine on later versions.
When Android gets API or behavior changes that have the potential to break old apps, the change only takes effect on apps that target the new API or higher. So all the old apps sitting in the store that haven't been updated will not be affected by the new API, because they don't target the new API.
I release LibGDX apps that target 20 and go to min version 9. These apps are installable and run fine on any device running Gingerbread or higher. I always compile with the latest SDK because I don't want to bother with keeping multiple SDK versions installed.
I have an app in the market that is targeting Android SDK 23 at the moment.
My problem is that with the release of Android 6, users have to accept dangerous permissions at runtime. I have got my first crash regarding this and I want to solve it fast before it gets serious.
I want to do it correctly as Android recommend asking the user at runtime to accept the permission and if not, hide the feature and stuff. But that takes time and will be done in the future. :)
But, would be for now changing the targetSdkVersion to 22 be a valid solution? What would that mean for users with Android 6 that have already installed the app?
I hope my quiestion is clear, thanks a lot!
If an app targets the Marshmallow SDK, it means that the app is aware of the new features and can use them
I think that if you're not handling the permissions as Android 6 is supposed target it one API lower because this is the compatibility of you're app
Btw it is recommended to ask the critical permissions on the start of the app and the minor when needed.
Hope that I helped.
I am trying to decide what target API should I choose to build my next android app. I know that Gingerbread was a major upgrade over Froyo and thus I want to use API 10(2.3.3). Also the report from Google tells me that Gingerbread 2.3.3 now has 61.5% of market share(http://developer.android.com/resources/dashboard/platform-versions.html).
The thing is at this point of my project I am not very sure if the LocationManager and other API enchancement in Gingerbread will if of use, though my app will definitely use them. If I use 2.2 for development then I can target a greater audience.
My question is, will it be possible for 2.2(Froyo) users to install and run my 2.3.3(gingerbread) app if I dont use any new API's introduced in 2.3 SDK?
Edit : If the answer is no, what would you guys suggest me to do, being it March 2012 now and the pace with which updates are coming? Should developers start with minimum 2.3.3 now, seeing the bugfixes and enhancements been introduced in it, not to mention the top market shareholder.
You could target 10 as API level, but define a minSdkVersion of 8 or so in your manifest. This will enable users of Froyo devices to install your app. But you have to ensure, that you don't use any API calls which are exclusive to API level 10. If you need to use functions introduced in API level 10 you should use them via reflection and either reimplement the missing functionality for pre API level 10 or notify the user of the missing functionaltiy.
If you target your application at API 10, 2.2 users won't be able to install it, even if you don't use any new API methods.
If you keep your application at Android 2.2, 2.3 users will still be able to install and use it. See the documentation for more.