Amahi specific logging
One thing I would like to do is logging for debugging puposes, however, I would like to disable logging for the external releases.
I would like to do this as part of the release checklist and prior to distribution to others. The idea is that we do not leak information like urls, session tokens, etc. to users who may get the apk, either for testing or for more nefarious purposes.
To do this best is to do it in one place. I iOS we used a single function/method that we defined to use the standard OS logging via whatever system logging mechanism exists.
Can we do something like that here?
#1 Updated by Anonymous over 8 years ago
We use Android's built in logging facility logcat. The information on this page may help us strip logcat calls from release packages.
#4 Updated by cpg about 8 years ago
Let me give an example. I changed my proxy to be my local server and it probably will not work, however, I would like to easily turn something on, recompile and see the interactions with the api, proxy and the relay in the logcat.
- want to turn it on by a compilation flag (e.g. a constant definition, in C/C++ terms, a #define)
- we want to make sure it cannot be turned at run time, so for production/release, we want to turn this setting off and be sure it cannot be turned on
In the future we may want to also see other things other than what the api/pfe/relay APIs return.
#6 Updated by cpg about 8 years ago
- Status changed from Closed to Assigned
can you add a note in the README (or in a docs/DEBUGGING.md file or somesuch), on how to turn on debugging and use it?
it should be in a way a dummy like me could manage to turn logging on and add statements to log.
(note that this is low priority and should not take over higher priority items)
Also available in: Atom