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.
Related
I have a fairly specific question, and I couldn't find something that really addresses my scenario.
We have an app in the Play Store. It's been there for years with periodic updates. Most recent update would bomb out on upload, and the Play Store made me update to minSDK (edit for this typo, TARGET not MIN) 29. Did so, and upload proceeded fine, but rolling out is troublesome because that puts a lot of users outside the update path and future updates.
I have personal feelings about Android and what I consider to be an idiotic model of leaving the carriers and MFGs to handle updates resulting in exactly this situation as they are clearly preferential to selling newer phones to customers, but that's a whole other discussion.
I don't really know what to do next; the Play Store doesn't seem at all interested in letting me upload my AAB at anything less than API 29, and a big percentage of my users are on Android 8, with some on lower versions. They can install, but can not run; immediate startup crash, and I can't reproduce it.
Anyone more familiar with Android deployments have some ideas or thoughts that I'm (hopefully very clearly) missing? I can't mandate a bunch of people run out and get new phones, especially those on company-supplied devices, but I also can't believe there's no other recourse for me to get my users updated.
Everything I find in all the google stuff starts with: 1) Make sure you have the android 29 SDK:
(sigh)
Thoughts? Thanks!
Google Play does not require you to have a minSdkVersion of 29 but instead a targetSdkVersion of 29 as of December 2020.
You can change the minSdkVersion to the minimum android version you want to support but you must have a targetSdkVersion of 29 or higher.
Ultimately, the issue was an unlogged error that I couldn't reproduce in debug/dev/testing, and only appeared in Release level builds, per this:
https://github.com/flutter/flutter/issues/58479
I hate this platform.
Thanks, all.
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 need some clarifications on Android. For example I developed an application with min version of 2.3.3 and I uploaded to play store and next versions I mean coming versions was Implemented in min 4.0 because functions force me to do that. So How Play store will response ? Is it consider like new project or some thing else? What will happen for already installed 2.3.3 version user? Can any one explain this?
if you change the min SDK then users that dont have above 4.0 will not be able to get new versions of your app and they will be stuck on the version they have until they get a new device that meets you minimum sdk.
Its not a new project all you are doing is updating you current one
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
I have an app on the marketplace, minSdkVersion is set to "3". I want to change it to "4" in my next release. Will existing android 1.5 users be affected by this, if they already have my app installed? I'm hoping they can continue using the app as is, they just wouldn't see it appear in the marketplace anymore?
Android 1.5 users who have already installed the app won't be affected, but they won't be able to update the app and use newer versions. That's because the minSdkVersion is now 4, and they use Android 1.5. They will neither see any updates nor be able to install it (if they uninstall the current version).
They will continue to be able to use the application that is installed on their phone. However, if they remove it, they won't be able to download it again. It shouldn't remove it from their phone if they do an update, if that is what you are worried about. It just won't see the update.