otto proguard about otto

[23code]

when click the button,throw this exception:
11-27 11:24:44.515: E/DatabaseUtils(2951): Writing exception to parcel
11-27 11:24:44.515: E/DatabaseUtils(2951): java.lang.SecurityException: Permission Denial: get/set setting for user asks to run as user -2 but is calling from user 0; this requires android.permission.INTERACT_ACROSS_USERS_FULL
11-27 11:24:44.515: E/DatabaseUtils(2951): at com.android.server.am.ActivityManagerService.handleIncomingUser(ActivityManagerService.java:13082)
11-27 11:24:44.515: E/DatabaseUtils(2951): at android.app.ActivityManager.handleIncomingUser(ActivityManager.java:2038)
11-27 11:24:44.515: E/DatabaseUtils(2951): at com.android.providers.settings.SettingsProvider.callFromPackage(SettingsProvider.java:577)
11-27 11:24:44.515: E/DatabaseUtils(2951): at android.content.ContentProvider$Transport.call(ContentProvider.java:279)
11-27 11:24:44.515: E/DatabaseUtils(2951): at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:273)

[JakeWharton]

That has nothing to do with Otto. The exception tells you what is wrong.
On Nov 26, 2013 7:25 PM, "staryanwx" [email protected] wrote:

when click the button,throw this exception:
11-27 11:24:44.515: E/DatabaseUtils(2951): Writing exception to parcel
11-27 11:24:44.515: E/DatabaseUtils(2951): java.lang.SecurityException:
Permission Denial: get/set setting for user asks to run as user -2 but is
calling from user 0; this requires
android.permission.INTERACT_ACROSS_USERS_FULL
11-27 11:24:44.515: E/DatabaseUtils(2951): at
com.android.server.am.ActivityManagerService.handleIncomingUser(ActivityManagerService.java:13082)
11-27 11:24:44.515: E/DatabaseUtils(2951): at
android.app.ActivityManager.handleIncomingUser(ActivityManager.java:2038)
11-27 11:24:44.515: E/DatabaseUtils(2951): at
com.android.providers.settings.SettingsProvider.callFromPackage(SettingsProvider.java:577)
11-27 11:24:44.515: E/DatabaseUtils(2951): at
android.content.ContentProvider$Transport.call(ContentProvider.java:279)
11-27 11:24:44.515: E/DatabaseUtils(2951): at
android.content.ContentProviderNative.onTransact(ContentProviderNative.java:273)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/100#issuecomment-29357464
.

[23code]

this is otto demo(LocationActivity),i do not change anything. only add Proguard and packaged into APK and it exception. can you have a try packaged LocationActivity demo into APK .or help me solve the problem. thanks

[23code]

this is the demo project. http://pan.baidu.com/s/1Ca2xl
I am very happy to find this library, if because of confusion package cannot be used, it is very regrettable.

[imminent]

@staryanwx This looks like an Android permissions issue, according to that stack trace. The culprit is names as "requires android.permission.INTERACT_ACROSS_USERS_FULL". Don't believe that is an Otto or Proguard problem.

[23code]

@imminent @JakeWharton but "android.permission.INTERACT_ACROSS_USERS_FULL" is system permission.i has no way to solve this. can you help me ? did you use otto success when Proguard to apk?

[23code]

ps:otto use directly in debug mode

[23code]

i found the exception what i say above is not otto problem, that is my phone system problem.
but when Proguard packaged into APK, otto can not run is the fact.
hope fix , thanksss

[23code]

who can Proguard otto demo(LocationActivity) to apk , and run correct ？

[imminent]

Does it work with everything the same except no Proguard? If the exception
you're having isn't related to Otto how are we suppose to fix it through
Otto? (Again, for Proguard, since it's a permissions issue, it shouldn't be
a Proguard issue either)

If you can get past that exception and show one that is a diagnosable Otto
issue, or show that the permission exception is introduced solely by adding
Proguard, then we have something to go by. Right now there's isn't anything
we can tell you.

On Tuesday, November 26, 2013, staryanwx wrote:

who can Proguard otto demo(LocationActivity) to apk , and run correct ？

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/100#issuecomment-29365546
.

Dandré Allison [phone]
KeepandShare.com http://www.keepandshare.com

          Schedule & Share. Simply. Securely.

[loganj]

@imminent The exception was a red herring. The original issue is that if you proguard the sample, it fails unless you set appropriate configuration for proguard.

@staryanwx Thanks, but this is already documented on the website. I think we do not need to add it to the sample app.

[23code]

@loganj @imminent I am a Chinese,my english is poor, maybe I didn't express clearly. i mean when i proguard the sample app. it fails.
in debug mode is run Perfect.

[zhihuitang]

hi staryanwx, have you fixed the problem? I have the same problem with. My app run perfectly in Debug mode, but throws exception in non-debug mode.

[23code]

@TangGod not fixed the problem,i has give up to use it.

[zhihuitang]

谢谢你的回复。

我开发一个程序搞了1个多月，调试模式下运行都没有问题；最后准备发布的时候，在我手机上试了下，发现有问题。今天搜了一天，好多老外遇见了同样的问题，但都没有解决方案。

搞不定我的工作就要白费了。。。。。崩溃

On Mon, Dec 30, 2013 at 2:24 AM, staryanwx [email protected] wrote:

@TangGod https://github.com/tanggod not fixed the problem,i has give up
to use it.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/100#issuecomment-31330214
.

[23code]

@TangGod 我也是，用broadcast一样可以解决，就是比较麻烦

[loganj]

The solution to this problem is either:

1. Do not proguard the sample app.

or:

1. If you do proguard the sample app, configure proguard as documented.