I just got the OTA for JellyBean on my Nexus S. READ_LOGS apps seem to work as before.. I can see all the logs in alogcat.
is this a bug? On Sunday, July 8, 2012 10:26:47 PM UTC+3, Ievgenii Nazaruk wrote: > > Hi all, > > I've been working on an application for developers that uses > DropBoxManager. The DropBoxManager requires READ_LOGS permission to be > granted in order to query information from it. > > Today I've tested my application on newest (api 16) emulator before > releasing it to Google Play. It turned out that Android now refuses to > grant this permission to 3rd party applications. This is weird because I've > looked through all Jelly Bean's documented changes and couldn't find > anything that mentions READ_LOGS permission. > > So basically my questions: > > - Did anyone see this change documented? > - Can someone confirm this behavior on Galaxy Nexus with Jelly Bean on > it (the one released to attendees of Google I/O)? > > And questions to someone from Android team: > > - Why this breaking change wasn't described in documentations like > > READ_EXTERNAL_STORAGE<http://developer.android.com/reference/android/Manifest.permission.html#READ_EXTERNAL_STORAGE>was? > > > - What should developers and testers do in order to use those handy > utility applications that require READ_LOGS to be useful? Is there any way > to allow READ_LOGS to 3rd party applications without making custom build > (i.e. something in "Developer Options" that I could've missed)? > > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
