Wow, you can type fast :)
Wonder if it will show up a little later, as the Market infrastructure
caches up.
-- Kostya
03.03.2011 19:07, Mark Carter пишет:
Well, I was pretty stunned just now when I read that post from Dianne.
Partly because I didn't know about it before. Partly because I didn't
believe it. But mostly because of a huge can of nasty worms it could
open, should it be true.
So, I just tried it with one of my not-so-important apps on the Market.
* Originally published at min-level 3 and checked I could see it on my
Nexus One running 2.2.2 (level 8) - which I could.
* Next, I rebuilt the APK using min level 9, (and building using SDK 9)
* Then I published the new APK over the old one
* Finally, I cleared the data for the Market app and checked whether
the app was there (by querying my publisher name) and it wasn't. My
other apps were.
So, I guess that indicates, that it's not true...
On 3 March 2011 22:55, Kostya Vasilyev <[email protected]
<mailto:[email protected]>> wrote:
03.03.2011 18:12, TreKing пишет:
On Thu, Mar 3, 2011 at 6:33 AM, Mark Carter
<[email protected] <mailto:[email protected]>> wrote:
Therefore, in an ideal world (!), I would like the 1.5/1.6
users to use the existing, well-tested version and the other
users will get the newer stuff.
This is particularly problematic for paid apps. If you
increase the min SDK level and then a lower SDK user
reflashes his device, he will no longer be able to install
your app. He won't even see it on the Market. That will then
lead to support emails along with the cumbersome directions
on how to install a legacy APK manually.
http://groups.google.com/group/android-developers/msg/b6b513af1a351c95
Yes, this is at least something. Two problems though:
- It's not quite clear if that can be relied on (the Market team
is separate from Dianne's frameworks team, and they can change
this undocumented behavior at any time and without notice).
- It's difficult to update the .apk built for an older Android
version.
I think it would be great if it was possible to upload and manage
multiple APKs for the same package / signature.
Then the developer could easily update the version targeting 1.5 /
1.6 should the need arise. Or have a separate version for 3.0 and
up (using the native fragment implementation) and a version for
1.6+ (using the upoming fragment compatibility library, or no
fragments at all).
-- Kostya
-------------------------------------------------------------------------------------------------
TreKing <http://sites.google.com/site/rezmobileapps/treking> -
Chicago transit tracking app for Android-powered devices
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to
[email protected]
<mailto:[email protected]>
To unsubscribe from this group, send email to
[email protected]
<mailto:[email protected]>
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--
Kostya Vasilyev --http://kmansoft.wordpress.com
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to
[email protected]
<mailto:[email protected]>
To unsubscribe from this group, send email to
[email protected]
<mailto:android-developers%[email protected]>
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--
Kostya Vasilyev -- http://kmansoft.wordpress.com
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
