About a month back I started a thread here about possible corrupt
installs because uninstalls/reinstalls would solve the problem for the
user. However in that particular problem that didn't work for for the
one persistent user. I finally tracked it down to an Android OS bug in
the Calendar class. The user reported that when he entered a time for
certain years the time was off when displayed in the app. For locale
compatibility I had used the DateFormat class to properly format the
string.
I could not duplicate the error on the emulator nor my devices UNTIL I
changed to the time zone of the user. My tests showed that the bug did
not exist in the US, Western Europe and Japanese times zone but in many
Asian time zones I tested with a test app that ran 200 years of dates.
It was nailed down to the Calender class because after setting the time
calling get returned the off hour and minute. This bug occurs up
through 3.2 but not in 4.0. A workaround was simple to implement but
unless one tested a number of other time zones it is unlikely a
developer would have discovered it. I did some searches to see if the
bug had been reported but didn't find an issue report. But then if it
was fixed in 4.x then it was a known bug.
- Brian
--
You received this message because you are subscribed to the Google Groups "Android
Discuss" 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-discuss?hl=en.
