We use ProGuard with our Android app and we haven't had any problems with it. It's kind of a pain to get it set-up properly but, once it's in place, it seems reliable. You can tell ProGuard to dump a map that allows you to easily translate the shortened, meaningless method names you'll see in the Developer Console stacktraces back to their original names in your source.
On Sep 10, 2:35 pm, Lance Nanek <[email protected]> wrote: > Some obfuscations make your code smaller/faster, like ProGuard > changing all your method names to a(), b(), etc.. You also never look > at the code after running it. Thinks like stack traces have to be > translated back by a tool. > > On Sep 7, 2:19 pm, DanH <[email protected]> wrote: > > > > > You can use an obfuscator (and, in fact, many Android experts > > recommend doing so). But it makes your code slower and larger and > > more difficult for you to maintain, and is of dubious effectiveness if > > someone really wants to "crack" your code badly enough. > > > On Sep 5, 11:38 pm, xc s <[email protected]> wrote: > > > > My English is just so-so . I dont 'want to other people > > > reversepengineering. my android app. how should I do? -- 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
