Unlikely, since I suddenly got a bunch of one-star "uh appilcatoin doesnt run under 1.6 lame" ratings. Well, if I could reply, I'd say that there is no official 1.6 out yet, but still.
Assuming "MM-dd-yyyy" if the result is either null or an empty string fixed the problem. -Mike On Oct 1, 9:13 am, Max_well <maxouw...@gmail.com> wrote: > I think (hope) it's an emulator bug. > > I filled a bug btw :http://code.google.com/p/android/issues/detail?id=3973 > > Simon > > On Oct 1, 7:44 am, EboMike <ebom...@gmail.com> wrote: > > > Settings.System.getString(resolver, Settings.System.DATE_FORMAT) > > returns null if the user never made a selection. > > > If the user does choose a date format and then switches back to > > default format, getString() will return "". > > > That was not the case before (and is breaking apps that relied on a > > valid string). What should an app assume if the return value is null > > or ""? Just "MM-dd-yyyy"? > > > -Mike > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
