On Mon, Apr 5, 2010 at 10:42 AM, HeHe <[email protected]> wrote: > but what i need is some info telling my apk that it was a debug or release > built without changing the "debuggable" attribute in manifest each time > between debug/release builds. >
This is not possible. You will have to make sure to remember to change that "debuggable" flag. Maybe add some code that sets your primary layout's background color to red in debug mode or something if you're so worried about it so you always know that you have that flag set. > i need it because in case i forget to change the debuggable attribute of my > release built to false my apk can still behave correctly. > So you don't really NEED it ... you just have to be careful before publishing your app. Even a rudimentary test on your release APK should alert you that you still have the debuggable flag set (for example, by setting your background to red in debug mode), in which case it takes about 2 seconds to switch it and rebuild. (1). i dont want to change the debuggable attribute in manifest between > debug and release builds. > You should. http://developer.android.com/intl/fr/guide/publishing/preparing.html Read section 4 In fact, as far as Android is concerned, that debuggable flag is pretty much what defines "DEBUG" vs "RELEASE", AFAIK. ------------------------------------------------------------------------------------------------- TreKing - Chicago transit tracking app for Android-powered devices http://sites.google.com/site/rezmobileapps/treking -- 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 To unsubscribe, reply using "remove me" as the subject.
