On Fri, Jul 10, 2009 at 1:25 PM, Mark Murphy<[email protected]> wrote: > Dan Bornstein wrote: >> That message is only ever produced because of entirely local >> information about a class, and the trigger condition is exactly as >> stated [...] > > I apologize for my mistake -- I was thinking of a different dex error.
No worries. > That being said, recompiling the code in question is the only way that I > know of to perhaps get past this problem. Yep, that's almost certainly the right way to proceed. I never meant to dispute that. Further cheers, -dan --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
