Thanks bro --
I realize it's not much code (or hard to write) but it is silly that a
year later, the Android Market still isn't up to speed. What happened
to not repeating yourself in code?
Peace,
Scott
On Dec 18, 12:32 pm, TreKing wrote:
> > So how do I get my users up to the current publishe
>
> So how do I get my users up to the current published version when my app
> was deployed without the check-this-web-file-version-by-hand-code and I
> don't even know who my users are?
Is it absolutely crucial that your users have the most recent update the
second it's put out? If not, don't wo
Wow! So the messages on this forum from over a year ago are still
applicable today? It is incomprehensible to expect every app
developer to write this code and that to notify users about updates?
So how do I get my users up to the current published version when my
app was deployed without the che
I wouldn't rely on those Market update notifications. Personally, I never
get them when they should kick in. Instead I usually check My Downloads
manually and, AFTER I've checked, the notification will kick in. And, not
only is it ridiculously late, it usually tells me the wrong number of
updates a
Thanks Vytautas --
I was careful to update both android:versionCode and
android:versionName before I uploaded my new apk. However, none of my
beta testers have received an update notification and it has been over
a week now. I have read myriad comments about users not receiving
update notificat
You don't have to do much else apart from uploading the new .apk onto
Android Market. The only thing you have to take care of is versioning
in the AndroidManifest.xml. Excellent resource on that is
http://developer.android.com/guide/publishing/versioning.html
The older posts that you found were pr
6 matches
Mail list logo