I have my own logging solution in my app, and even though it's very useful...
... being able to see the system logs is invaluable and irreplaceable in some situations. For example, I recently experienced LVL validation failures and asked the users to use CatLog (one the of apps on Market that can read and email logcat output). With the logcat output in hand, it was obvious that the failure is on Google's side (again!) and I knew what to do about it. I understand that the Android team's concern, as was previously mentioned on the list, is for applications that may print personal user's information in the system log. Why, then, is the remedy such that it punishes apps that are not in violation of the user's privacy with their logcat use? Is the actual install share of JB so high already that this change is believed to be a meaningful solution? -- K 2012/7/12 Latimerius <[email protected]> > The upcoming ACRA release will (probably) contain the ability to > include a custom application-private log file in a report. So if you > only care for reading the system log to read your own log messages, > that should be taken care of. Of course, if you really want to read > the actual stuff logged by the system and other apps, that's going to > be tougher. > > On Thu, Jul 12, 2012 at 5:19 PM, b0b <[email protected]> wrote: > > The thing is that it is better to not rely on READ_LOGS to (for example) > > provide logs to ACRA. > > The bonus is that your app will not need that permission which is kind of > > scary. > > > > How can it be done ? > > > > - wrap all your logging calls into functions adding your log message + > any > > other metadata (like tag or timestamp) to a cache were you keep the last > n > > log lines. Can be done with a simple LinkedHashMap overriding > > removeEldestEntry(). > > - modify ACRA by adding a custom column that will contain the content of > > the log cache. When the crash report is constructed, fill that column > with > > the cache data > > - profit! > > > > > > > > -- > > 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 > > -- > 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 > -- 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
