We've got a pretty popular app that was working fine on all the versions of Android 2.2 and before. When the 2.3 versions started to become more common, we started getting complaints relating to errors that are originating from the fact that one Activity will write a user setting and then launch another activity, whereas the newly launched activity will read that user setting and then operate on it. Problem is, when the new activity goes to grab the user setting, OCCASSIONALLY it won't yet be set, thereby making the new activity not display correctly. This exact code works 100% of the time in versions 2.2 and prior. Only in 2.3+ does it SOMETIMES break. I'd be happy if it broke all the time so I could fix it, but this intermittent stuff has me stymied. Any help would be much appreciated.
-- 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
