Home/ Questions/Q 8540049
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-11T11:30:43+00:00

In C++ I would normally setup 2 builds – debug and release with each

  • 0

In C++ I would normally setup 2 builds – debug and release with each having DEBUG and RELEASE predefined respectively. I would then use these definitions to determine constant values, like logging enabled/disabled, server URL and etc.

Right now, in Java/Android I comment out some stuff before building release. That is not a good way, I can tell. I may forget something.

What is a common practice for ensuring nothing is forgotten when building a release version (signed) or debug version (unsigned)?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    There’s no (by default) any preprocessor for Java, so no #ifdef stuff at compile time. But if you do not mind leaving debug code in your app, then you can check if app is release or debug at runtime with this code:

    Boolean release = (getApplicationInfo().flags & ApplicationInfo.FLAG_DEBUGGABLE);

    which checks debuggable flag value. And said flad is automatically set to false for release builds and true for debug builds.

    If you want to get rid of some debug code, you may try using ProGuard to strip certain classes or methods. And by default ProGuard is involved in building process for release builds only.

    • 0