{"id":80,"date":"2014-03-03T06:23:39","date_gmt":"2014-03-03T06:23:39","guid":{"rendered":"https:\/\/cindypotvin.com\/?p=80"},"modified":"2017-02-18T16:37:00","modified_gmt":"2017-02-18T21:37:00","slug":"creating-logs-in-android-applications","status":"publish","type":"post","link":"https:\/\/cindypotvin.com\/creating-logs-in-android-applications\/","title":{"rendered":"Creating logs in Android applications"},"content":{"rendered":"<p>For Android applications, logging is handled by the <em>android.util.Log<\/em> class, which is a basic logging class that stores the logs in a circular buffer for the whole device. All logs for the device can be seen in the LogCat tab in Eclipse, or read using the <em>logcat<\/em> command. Here is a standard log output for the LogCat tab in Eclipse :<\/p>\n<p><a href=\"https:\/\/cindypotvin.com\/wp-content\/uploads\/2014\/03\/image.png\"><img loading=\"lazy\" decoding=\"async\" style=\"display: inline; background-image: none;\" title=\"image\" alt=\"image\" src=\"https:\/\/cindypotvin.com\/wp-content\/uploads\/2014\/03\/image_thumb.png\" width=\"1084\" height=\"291\" border=\"0\" \/><\/a><\/p>\n<p>There are five levels of logs you can use in your application, for the most verbose to the least verbose :<\/p>\n<ul>\n<li><strong>Verbose:<\/strong>For extra information messages that are only compiled in a debug application, but never included in a release application.<\/li>\n<li><strong>Debug:<\/strong> For debug log messages that are always compiled, but stripped at runtime in a release application.<\/li>\n<li><strong>Info:<\/strong> For an information in the logs that will be written in debug and release.<\/li>\n<li><strong>Warning:<\/strong> For a warning in the logs that will be written in debug and release.<\/li>\n<li><strong>Error:<\/strong> For an error in the logs that will be written in debug and release.<\/li>\n<\/ul>\n<p>A log message includes a tag identifying a group of messages and the message. By default the log level of all tags is <em>Info<\/em>, which means than messages that are of level <em>Debug<\/em> and <em>Verbose<\/em> should never shown unless the setprop command is used to change the log level. So, to write a verbose message to the log, you should call the isLoggable method to check if the message can be logged, and call the logging method :<\/p>\n<pre class=\"brush: java;\">if (!Log.isLoggable(logMessageTag, Log.Verbose))\r\n   Log.v(\"MyApplicationTag\", logMessage);<\/pre>\n<p>And to show the Debug and Verbose log message for a specific tag, run the setprop command while your device is plugged in. If you reboot the device you will have to run the command again.<\/p>\n<pre class=\"brush: text; gutter: false\">adb shell setprop log.tag.MyApplicationTag VERBOSE<\/pre>\n<p>Unfortunately, starting\u00a0 with Android 4.0, an application can only read its own logs. It was useful for debugging to be able to read logs from another application, but in some cases sensitive information was written in those logs, and malicious apps were created to retrieve them. So if you need to have logs files send to you for debugging, you will need to create your own log class using the methods from the <em>android.util.Log<\/em> class. Remember, only <em>Info<\/em>, <em>Warning<\/em> and <em>Error<\/em> logs should be shown when the application is not run in debug mode.\u00a0 Here is an example of a simple logger wrapping the call to <em>isLoggable<\/em> and storing the logs messages on the primary storage of the device (requires the permission WRITE_EXTERNAL_STORAGE) and to the standard buffer :<\/p>\n<pre class=\"brush: java;\">\/**\r\n  * A logger that uses the standard Android Log class to log exceptions, and also logs them to a \r\n  * file on the device. Requires permission WRITE_EXTERNAL_STORAGE in AndroidManifest.xml.\r\n  * @author Cindy Potvin\r\n  *\/\r\n public class Logger\r\n {\r\n \/**\r\n   * Sends an error message to LogCat and to a log file.\r\n   * @param context The context of the application.\r\n   * @param logMessageTag A tag identifying a group of log messages. Should be a constant in the \r\n   *                      class calling the logger.\r\n   * @param logMessage The message to add to the log.\r\n   *\/\r\n public static void e(Context context, String logMessageTag, String logMessage) \r\n    {\r\n    if (!Log.isLoggable(logMessageTag, Log.ERROR))\r\n       return;\r\n\r\n    int logResult = Log.e(logMessageTag, logMessage);\r\n    if (logResult > 0) \r\n       logToFile(context, logMessageTag, logMessage);\r\n    }\r\n\r\n\/**\r\n   * Sends an error message and the exception to LogCat and to a log file.\r\n   * @param context The context of the application.\r\n   * @param logMessageTag A tag identifying a group of log messages. Should be a constant in the \r\n   *                      class calling the logger.\r\n   * @param logMessage The message to add to the log.\r\n   * @param throwableException An exception to log\r\n   *\/\r\n public static void e(Context context, String logMessageTag, String logMessage, Throwable throwableException) \r\n    {\r\n    if (!Log.isLoggable(logMessageTag, Log.ERROR))\r\n       return;\r\n\r\n    int logResult = Log.e(logMessageTag, logMessage, throwableException);\r\n    if (logResult > 0) \r\n       logToFile(context, logMessageTag, logMessage + \"\\r\\n\" + Log.getStackTraceString(throwableException));\r\n    }\r\n\r\n\/\/ The i and w method for info and warning logs should be implemented in the same way as the e method for error logs.\r\n\r\n\/**\r\n   * Sends a message to LogCat and to a log file.\r\n   * @param context The context of the application.\r\n   * @param logMessageTag A tag identifying a group of log messages. Should be a constant in the \r\n   *                      class calling the logger.\r\n   * @param logMessage The message to add to the log.\r\n   *\/\r\n public static void v(Context context, String logMessageTag, String logMessage) \r\n    {\r\n                              \/\/ If the build is not debug, do not try to log, the logcat be \r\n                              \/\/ stripped at compilation.\r\n    if (!BuildConfig.DEBUG || !Log.isLoggable(logMessageTag, Log.VERBOSE))\r\n        return;\r\n\r\n    int logResult = Log.v(logMessageTag, logMessage);\r\n    if (logResult > 0) \r\n       logToFile(context, logMessageTag, logMessage);\r\n    }\r\n\r\n\/**\r\n   * Sends a message and the exception to LogCat and to a log file.\r\n   * @param logMessageTag A tag identifying a group of log messages. Should be a constant in the \r\n   *                      class calling the logger.\r\n   * @param logMessage The message to add to the log.\r\n   * @param throwableException An exception to log\r\n   *\/\r\n public static void v(Context context,String logMessageTag, String logMessage, Throwable throwableException) \r\n    {\r\n                              \/\/ If the build is not debug, do not try to log, the logcat be \r\n                              \/\/ stripped at compilation.\r\n    if (!BuildConfig.DEBUG || !Log.isLoggable(logMessageTag, Log.VERBOSE))\r\n        return;\r\n\r\n    int logResult = Log.v(logMessageTag, logMessage, throwableException);\r\n    if (logResult > 0) \r\n       logToFile(context, logMessageTag,  logMessage + \"\\r\\n\" + Log.getStackTraceString(throwableException));\r\n    }\r\n\r\n\/\/ The d method for debug logs should be implemented in the same way as the v method for verbose logs.\r\n\r\n\/**\r\n  * Gets a stamp containing the current date and time to write to the log.\r\n  * @return The stamp for the current date and time.\r\n  *\/\r\n private static String getDateTimeStamp()\r\n    {\r\n    Date dateNow = Calendar.getInstance().getTime();\r\n                              \/\/ My locale, so all the log files have the same date and time format\r\n    return (DateFormat.getDateTimeInstance(DateFormat.SHORT, DateFormat.SHORT, Locale.CANADA_FRENCH).format(dateNow));\r\n    }\r\n\r\n\/**\r\n  * Writes a message to the log file on the device.\r\n  * @param logMessageTag A tag identifying a group of log messages.\r\n  * @param logMessage The message to add to the log.\r\n  *\/\r\n private static void logToFile(Context context, String logMessageTag, String logMessage)\r\n    {\r\n    try\r\n       {\r\n                              \/\/ Gets the log file from the root of the primary storage. If it does \r\n                              \/\/ not exist, the file is created.\r\n       File logFile = new File(Environment.getExternalStorageDirectory(), \"TestApplicationLog.txt\");\r\n       if (!logFile.exists())\r\n          logFile.createNewFile();\r\n                              \/\/ Write the message to the log with a timestamp\r\n       BufferedWriter writer = new BufferedWriter(new FileWriter(logFile, true));\r\n       writer.write(String.format(\"%1s [%2s]:%3s\\r\\n\", getDateTimeStamp(), logMessageTag, logMessage));\r\n       writer.close();\r\n                              \/\/ Refresh the data so it can seen when the device is plugged in a \r\n                              \/\/ computer. You may have to unplug and replug to see the latest \r\n                              \/\/ changes\r\n      MediaScannerConnection.scanFile(context, \r\n                                      new String[] { logFile.toString() }, \r\n                                      null, \r\n                                      null);\r\n\r\n       }\r\n    catch (IOException e)\r\n       {\r\n       Log.e(\"com.cindypotvin.Logger\", \"Unable to log exception to file.\");\r\n       }\r\n    }\r\n }<\/pre>\n<p>If you release an application to the app store or to a client with this kind of logger, you should disable logging by default and add a switch in the preferences to enable logging on demand. If the logger is always enabled, your application will often write to the primary storage and to the logcat, which is an unnecessary overhead when everything works correctly. Also, the size of the log file should be limited in some way to avoid filling up the primary storage.<iframe loading=\"lazy\" src=\"https:\/\/newsletter.cindypotvin.com\/embed\" width=\"100%\" height=\"320\" frameborder=\"0\" scrolling=\"no\"><\/iframe><\/p>\n<!--themify_builder_content-->\n<div id=\"themify_builder_content-80\" data-postid=\"80\" class=\"themify_builder_content themify_builder_content-80 themify_builder tf_clear\">\n    <\/div>\n<!--\/themify_builder_content-->\n","protected":false},"excerpt":{"rendered":"<p>For Android applications, logging is handled by the android.util.Log class, which is a basic logging class that stores the logs in a circular buffer for the whole device. All logs for the device can be seen in the LogCat tab in Eclipse, or read using the logcat command. Here is a standard log output for [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2,15,3,4],"tags":[8,12,18,19,20],"jetpack_featured_media_url":"","jetpack-related-posts":[],"jetpack_sharing_enabled":true,"builder_content":"","_links":{"self":[{"href":"https:\/\/cindypotvin.com\/wp-json\/wp\/v2\/posts\/80"}],"collection":[{"href":"https:\/\/cindypotvin.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cindypotvin.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cindypotvin.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cindypotvin.com\/wp-json\/wp\/v2\/comments?post=80"}],"version-history":[{"count":9,"href":"https:\/\/cindypotvin.com\/wp-json\/wp\/v2\/posts\/80\/revisions"}],"predecessor-version":[{"id":1482,"href":"https:\/\/cindypotvin.com\/wp-json\/wp\/v2\/posts\/80\/revisions\/1482"}],"wp:attachment":[{"href":"https:\/\/cindypotvin.com\/wp-json\/wp\/v2\/media?parent=80"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cindypotvin.com\/wp-json\/wp\/v2\/categories?post=80"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cindypotvin.com\/wp-json\/wp\/v2\/tags?post=80"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}