I have a similar situation and would like to know. I have posted a similar question in this group and gotten the answer, "use reflection instead." That may be useful in many situations, and I always appreciate suggestions, but it is not always feasible. It's good to know so as not to leave existing users with a bad experience.
On Aug 22, 10:54 pm, scadaguru <scadag...@gmail.com> wrote: > Hi All, > I have a published application now if I upgrade minSdk requirement to > higher level what will happen? > 1. Published application has minSdk set to 3 that is OS V1.5 > 2. Now if I increase it to 5 (OS v2.0) and republish (upload upgrade) > people using older OS than 2.0 who already have installed my > application I believe will not see in the market but still will be > able to run from the phone. And once they uninstall it will be gone > for ever. Is that right? > 3. What is good practice? What should I do? Have another application > published with higher OS version requirement or upgrade original. My > application is free app so no money is involve. 4 > 4. If I publish new application while keeping old one with lower OS > version in the market intact, how the people will know that they have > update available who already have installed my applicaiton but has the > phone with higher OS and could run my second application? > > Please advice. > Thanks, > JP -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
