[android-developers] Ant build with Proguard (per blog) not obfuscating

2010-09-24 Thread Anm

The timing of this week's blog post was perfect.  It was exactly what
I intended to do today.  And the extra Ant step worked fine, and I can
see Proguard obfuscate my files into bin/obf/obfuscated.jar (yes, I
tweaked the file names and paths a little bit), the resulting App-
release.apk does not include the obfuscated files.  My first hint was
my stack traces, but I confirmed it with dedexer.

Has anyone else verified their .apk?  How does the compile step know
what .class files to use? (I'm hoping its not assuming some hard coded
path.)


Anm

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


Re: [android-developers] Ant build with Proguard (per blog) not obfuscating

2010-09-24 Thread Xavier Ducrohet
some classes will not be obfuscated like classes extending Activity,
Service, and other classes referenced in the manifest.

The way the obfuscation works is that it creates a jar file of your
application code (should be in bin/obf/original.jar I think) which is
then obfuscated.

This is the line:
  jar basedir=${out.classes.dir} destfile=${android-jar-preobfuscate} /
in the ant xml fragment you import into your build file.

since you changed the file names a bit make sure the line
property name=out.dex.input.absolute.dir
value=${android-jar-postobfuscate} /
still sets the out.dex... prop to contain the proguard'ed jar file.

On Fri, Sep 24, 2010 at 2:22 AM, Anm andrew.n.marsh...@gmail.com wrote:

 The timing of this week's blog post was perfect.  It was exactly what
 I intended to do today.  And the extra Ant step worked fine, and I can
 see Proguard obfuscate my files into bin/obf/obfuscated.jar (yes, I
 tweaked the file names and paths a little bit), the resulting App-
 release.apk does not include the obfuscated files.  My first hint was
 my stack traces, but I confirmed it with dedexer.

 Has anyone else verified their .apk?  How does the compile step know
 what .class files to use? (I'm hoping its not assuming some hard coded
 path.)


 Anm

 --
 You received this message because you are subscribed to the Google
 Groups Android Developers group.
 To post to this group, send email to android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en




-- 
Xavier Ducrohet
Android SDK Tech Lead
Google Inc.

Please do not send me questions directly. Thanks!

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en