There is an associated StackOverflow question here, which has more details but still no answer http://stackoverflow.com/questions/8762281/proguard-and-dalvik-error-code-1
On Wednesday, 14 March 2012 16:35:11 UTC, Alex Curran wrote: > > A while back I tried to create an implementation of CursorLoaders in my > app, switching from managedQuery()s. I found that this resulted in my app > failing to obfuscate when running it through ProGuard, returning with a > dialog which references Error 1, but giving no other details. I surmised it > was because I was using a complicated method of routing callbacks through > my app and thought nothing more of it. > > I tried again today, using the most basic implementation I could > (analogous to the implementation in the Loaders article in the Android > Developers website with one Activity implementing the Callbacks), and again > it failed to obfuscate. Removing any references to the Loader framework > resulted it in building and obfuscating correctly. > > Is this a known problem or something very odd? It's probably worth noting, > I'm using the support library (v6), and the app will build fine, run fine > and even compile for release *so long as it isn't run through ProGuard*. > -- 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
