kris, You're right, a "bug" is not an accurate way to describe a hard-to- diagnose failure mode that may be due to a possible platform misconfiguration. Perhaps we should call it "job security for Android developers".
My main point was to document a possible workaround in the forum in case others hit the same failure mode - adding to the folk knowledge of Android. :) On Dec 9, 8:26 am, Kristopher Micinski <[email protected]> wrote: > > P.s., glad you got it working, but still doubtful there's an sdk bug... > > I should correct, I'm confident that there is *an* sdk bug, I'm just > not sure that particular bug is causing this problem :-) > > kris -- 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
