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
Related
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 have a problem with flurry for android. I don't see last app version in filter several days (about 5 days). Later new version got to version list in filter very fast.
Also if check "TOP 10 VERSIONS BY ACTIVE USERS" i can suppose that my new version is saved as other. I upload new version 20 march and on graph i see that version other grow from 20 march.
I use SDK version 6.6.0. Now i upgraded to 6.9.2. Later flurry determined version of app without problem.
For init flurry i use the following code:
new FlurryAgent.Builder()
.withLogEnabled(true)
.withListener(getFlurryAgentListener())
.build(context, MY_API_KEY);
Can anyone say what i do wrong or how to solve this problem?
Your app has more than 1000 app versions.
To correct this you will need to delete some older versions you no longer need.
Currently this can only be done in the old 'Flurry Classic' site. See here:
We will be adding this feature to the new Flurry site soon.
Finally you can avoid problems with the version limit by using separate project api keys for development/testing versus the published version of the app.
I'm currently involved in an open source project which I regulary release in the Google PlayStore. As the statistics of android-usages show that less than 10% of my users use android 3 or lower I started to wonder if I should switch to Android 4.X. This gives me some more functionality which I can't include at the moment (SettingsFragment for example, which isn't even inside of the support library).
When I release a newer version with higher requirements in the PlayStore - what will happen to my users which don't fulfill this requirements? What about users who want to install my app with low android-versions? Is my app hidden for them as soon as I upgrade the app? Is there any chance that my current version of my app can still be found by lower devices and the newer version is available for newer devices? I would like to avoid having two seperate apps in the playstore as I would lose a few people.
I couldn't find anything in the Google-Docs so I needed to ask for help in this glory community ;)
You can target multiple different APIs using multiple APK's. Just use your current version for old versions and create a new APK for everyone else. More here: http://developer.android.com/google/play/publishing/multiple-apks.html
Hope this helps, let me know if you need more info.
I want to ask if is it ok that i update already posted version on android market. Like i have version 5.0 and 4.0 on android market. If i want to remove 5.0 from android market and make changes to it and post back the 5.0 version. Is there any implications to that. Is there any problem with this approach?
You should change the version no to something great than existing version no. This is required so that android market client knows that a new version is available and it notifies the user to update the app.
SoundPool has a serious bug in it in Android 1.5. I fixed it with a workaround, but since it really limits my app, I want to target 1.6+ for the next version of it.
I am wondering: What happens when I release a upgrade that has a higher target SDK version then the previous version of my app? Will only 1.6+ users be able to upgrade their app? Or will also the 1.5 users be able to upgrade since they have the program already installed?
Anybody experience with this?
Since you answered one of my questions, I thought I'd take a look at your questions:-
From what I've read on the Android dev site:-
The manifest holds the MINIMUM version that the APK will support. Only users with the same version or higher of that SDK will be able to even see you App in the Market.
Therefore, to answer your question, YES, only users with OS 1.6+ Android will be able to upgrade. I released an app once, set to 1.6, and wondered why I was getting less downloads, then realised what I had done, set it back to 1.5, and all was well.
Is there anyway you could get the newer 1.6 source for soundpool, add that to your app, and use it when version 1.5 is detected (or, just use it all the time).
Lots of hassle I know, but just a thought.
Havn't got any experience with this but that a 1.5 user can use an app targeted for minimum 1.6 seems highly unlikely. They will probably be informed that your app no longer supports their platform or just not recive the update.