LogCat field broken by Jelly Bean changes

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Configure ACRA to send the LogCat field
2. Send an ACRA report from a Jelly Bean device

What is the expected output? What do you see instead?
Expected to see the LogCat logs like with every other OS version, but see 
nothing instead instead.

What version of the product are you using? On what operating system?
4.2.3 - Android?

Please provide any additional information below.

I realize that an undocumented change was made by the Android team for Jelly 
Bean which restricts the READ_LOGS permission to no longer be granted to an 
application in a production runtime environment.  The discussion on that can be 
found here: 
https://groups.google.com/forum/?fromgroups#!topic/android-developers/6U4A5irWan
g%5B1-25%5D
And the official issue opened can be found here: 
http://code.google.com/p/android/issues/detail?id=34792

I believe this change is breaking the ACRA LogCat field.  However, in that 
thread it also mentions that if you use Runtime.getRuntime().exec("logcat -t 
50"); Jelly Bean will realize you don't have READ LOGS permissions, and will 
return only your own application's related logging.  I have tested this myself 
and it's working.  So I would have expected the LogCat field to at least report 
the logged lines of our own application in Jelly Bean, but it's not sending 
anything for the LogCat field.

Original issue reported on code.google.com by Bubb...@gmail.com on 15 Aug 2012 at 6:31

[GoogleCodeExporter]

Thank you for these links, I'll try to implement a workaround for JellyBean 
ASAP to get at least the logs we will be authorized to get.

Original comment by kevin.gaudin on 15 Aug 2012 at 8:45

• Added labels: Milestone-Release4.3, Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Change commited in the trunk. Will be packaged in 4.3.0b2

Original comment by kevin.gaudin on 16 Aug 2012 at 8:12

• Changed state: Fixed

[GoogleCodeExporter]

Thanks for your quick response and subsequent fix.  I'm looking forward to 
4.3.0b2 :)

Original comment by Bubb...@gmail.com on 16 Aug 2012 at 4:43

[GoogleCodeExporter]

4.3.0b2 is published.

Original comment by kevin.gaudin on 16 Aug 2012 at 9:23

[GoogleCodeExporter]

Got a chance to install the new version into our app and it's sending us LogCat 
logs in Jelly Bean now!  I'm sure you tested on your side but I just wanted to 
followup so you knew it's fixed on our end too :)  Thanks!

Original comment by Bubb...@gmail.com on 16 Aug 2012 at 10:27

[GoogleCodeExporter]

Thanks a lot for testing !

Original comment by kevin.gaudin on 16 Aug 2012 at 10:58

• Changed state: Verified

[GoogleCodeExporter]

Any idea why logcat is sometimes empty? This is happening on 4.1.1 at least 
with Nexus 7, but I don't have many reports yet. Since PREF_ENABLE_SYSTEM_LOGS 
defaults to 'true' this should work without any additional configuration, right?

Original comment by nikolay....@gmail.com on 5 Sep 2012 at 6:08