Could you do:
$ ./gradlew assemble
and then check the contents of the files:
build/source/buildConfig/<buildtype>/your/package/BuildConfig.java and
paste the line that looks like:
public static final boolean DEBUG = Boolean.parseBoolean("true");
If it shows false, then could you create a bug and attach your
reproducible test case to it? Thanks.
On Sat, Feb 22, 2014 at 7:31 AM, Scott Adams <[email protected]> wrote:
> I have seen some similar posts about this such as
> https://groups.google.com/forum/#!topic/adt-dev/lyeeJTEGyhQ but I am not
> sure if this is related. It seems that debuggable is completely ignored in
> the buildTypes and is always false.
>
> buildTypes {
> debug {
> packageNameSuffix ".debug"
> debuggable true
> jniDebugBuild true
> }
> release {
> debuggable false
> jniDebugBuild false
> runProguard true
> proguardFiles getDefaultProguardFile('proguard-android.txt'),
> 'proguard-rules.txt'
> signingConfig signingConfigs.release
> }
> }
>
> BuildConfig.DEBUG always returns false.
>
> The .debug suffix works so I am using that as a workaround to identify the
> debug build.
>
> --
> You received this message because you are subscribed to the Google Groups
> "adt-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
"adt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
