Mixing
Crash - Sending non-protected broadcast
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
1
I've searched this log but everything I've seen just says it's a warning. For some background, this does NOT crash on Oreo, but it DOES crash on Pie. I have no idea what broadcast could be causing it.
I've put breakpoints at every place I call "sendBroadcast" and can confirm that the crash happens before any broadcast is sent from the app.
if you require any code from any class, let me know and I'll put it up immediately
Any idea why this would be crashing on Pie?
2019-01-03 09:18:09.043 879-1094/? W/ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1023 com.android.server.am.AppStateBroadcaster.broadcastAppState:125 com.android.server.am.AppStateBroadcaster.sendApplicationFocusGain:49 com.android.server.am.OnePlusAmUtil$OnePlusActivityManagerService$1.run:346 android.os.Handler.handleCallback:873
2019-01-03 09:18:09.043 879-6821/? I/ActivityManager: Process com.android.chrome:sandboxed_process0 (pid 31022) has died: fore SVC
2019-01-03 09:18:09.043 1959-1959/? D/QcrilMsgTunnelIfaceManager: handleMessage what = 1
2019-01-03 09:18:09.043 1801-1801/? I/Zygote: Process 31022 exited cleanly (0)
2019-01-03 09:18:09.046 1959-1959/? I/QcrilOemhookMsgTunnel: [0]invokeOemRilRequestRaw: serial=4446 length=24
2019-01-03 09:18:09.047 879-1094/? E/ActivityManager: Sending non-protected broadcast diagandroid.app.ApplicationState from system 879:system/1000 pkg android
java.lang.Throwable
at com.android.server.am.ActivityManagerService.checkBroadcastFromSystem(ActivityManagerService.java:23205)
at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:23790)
at com.android.server.am.ActivityManagerService.broadcastIntent(ActivityManagerService.java:24025)
at android.app.ContextImpl.sendBroadcast(ContextImpl.java:1029)
at com.android.server.am.AppStateBroadcaster.broadcastAppState(AppStateBroadcaster.java:125)
at com.android.server.am.AppStateBroadcaster.sendApplicationFocusGain(AppStateBroadcaster.java:49)
at com.android.server.am.OnePlusAmUtil$OnePlusActivityManagerService$1.run(OnePlusAmUtil.java:346)
at android.os.Handler.handleCallback(Handler.java:873)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:193)
at android.os.HandlerThread.run(HandlerThread.java:65)
at com.android.server.ServiceThread.run(ServiceThread.java:44)
android asked Jan 3 at 16:07
Psest328Psest328
3,16453463
add a comment |
1
I've searched this log but everything I've seen just says it's a warning. For some background, this does NOT crash on Oreo, but it DOES crash on Pie. I have no idea what broadcast could be causing it.
I've put breakpoints at every place I call "sendBroadcast" and can confirm that the crash happens before any broadcast is sent from the app.
if you require any code from any class, let me know and I'll put it up immediately
Any idea why this would be crashing on Pie?
2019-01-03 09:18:09.043 879-1094/? W/ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1023 com.android.server.am.AppStateBroadcaster.broadcastAppState:125 com.android.server.am.AppStateBroadcaster.sendApplicationFocusGain:49 com.android.server.am.OnePlusAmUtil$OnePlusActivityManagerService$1.run:346 android.os.Handler.handleCallback:873
2019-01-03 09:18:09.043 879-6821/? I/ActivityManager: Process com.android.chrome:sandboxed_process0 (pid 31022) has died: fore SVC
2019-01-03 09:18:09.043 1959-1959/? D/QcrilMsgTunnelIfaceManager: handleMessage what = 1
2019-01-03 09:18:09.043 1801-1801/? I/Zygote: Process 31022 exited cleanly (0)
2019-01-03 09:18:09.046 1959-1959/? I/QcrilOemhookMsgTunnel: [0]invokeOemRilRequestRaw: serial=4446 length=24
2019-01-03 09:18:09.047 879-1094/? E/ActivityManager: Sending non-protected broadcast diagandroid.app.ApplicationState from system 879:system/1000 pkg android
java.lang.Throwable
at com.android.server.am.ActivityManagerService.checkBroadcastFromSystem(ActivityManagerService.java:23205)
at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:23790)
at com.android.server.am.ActivityManagerService.broadcastIntent(ActivityManagerService.java:24025)
at android.app.ContextImpl.sendBroadcast(ContextImpl.java:1029)
at com.android.server.am.AppStateBroadcaster.broadcastAppState(AppStateBroadcaster.java:125)
at com.android.server.am.AppStateBroadcaster.sendApplicationFocusGain(AppStateBroadcaster.java:49)
at com.android.server.am.OnePlusAmUtil$OnePlusActivityManagerService$1.run(OnePlusAmUtil.java:346)
at android.os.Handler.handleCallback(Handler.java:873)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:193)
at android.os.HandlerThread.run(HandlerThread.java:65)
at com.android.server.ServiceThread.run(ServiceThread.java:44)
asked Jan 3 at 16:07
Psest328Psest328
3,16453463
1
Look in your logs for "FATAL" instead, as this may just be a red herring. If your application is actually crashing, you should get a stack trace.
– kcoppock
Jan 3 at 16:11
1
you were right! in 300 lines there's 1 reference to fatal: java.lang.NoClassDefFoundError: Failed resolution of: Lorg/apache/http/message/BasicNameValuePair; A search on stackoverflow gives me the answer to that. Thank you so much. Put this as an answer so I can give you a check mark!
– Psest328
Jan 3 at 16:17
add a comment |
1
1
1
I've searched this log but everything I've seen just says it's a warning. For some background, this does NOT crash on Oreo, but it DOES crash on Pie. I have no idea what broadcast could be causing it.
I've put breakpoints at every place I call "sendBroadcast" and can confirm that the crash happens before any broadcast is sent from the app.
if you require any code from any class, let me know and I'll put it up immediately
Any idea why this would be crashing on Pie?
2019-01-03 09:18:09.043 879-1094/? W/ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1023 com.android.server.am.AppStateBroadcaster.broadcastAppState:125 com.android.server.am.AppStateBroadcaster.sendApplicationFocusGain:49 com.android.server.am.OnePlusAmUtil$OnePlusActivityManagerService$1.run:346 android.os.Handler.handleCallback:873
2019-01-03 09:18:09.043 879-6821/? I/ActivityManager: Process com.android.chrome:sandboxed_process0 (pid 31022) has died: fore SVC
2019-01-03 09:18:09.043 1959-1959/? D/QcrilMsgTunnelIfaceManager: handleMessage what = 1
2019-01-03 09:18:09.043 1801-1801/? I/Zygote: Process 31022 exited cleanly (0)
2019-01-03 09:18:09.046 1959-1959/? I/QcrilOemhookMsgTunnel: [0]invokeOemRilRequestRaw: serial=4446 length=24
2019-01-03 09:18:09.047 879-1094/? E/ActivityManager: Sending non-protected broadcast diagandroid.app.ApplicationState from system 879:system/1000 pkg android
java.lang.Throwable
at com.android.server.am.ActivityManagerService.checkBroadcastFromSystem(ActivityManagerService.java:23205)
at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:23790)
at com.android.server.am.ActivityManagerService.broadcastIntent(ActivityManagerService.java:24025)
at android.app.ContextImpl.sendBroadcast(ContextImpl.java:1029)
at com.android.server.am.AppStateBroadcaster.broadcastAppState(AppStateBroadcaster.java:125)
at com.android.server.am.AppStateBroadcaster.sendApplicationFocusGain(AppStateBroadcaster.java:49)
at com.android.server.am.OnePlusAmUtil$OnePlusActivityManagerService$1.run(OnePlusAmUtil.java:346)
at android.os.Handler.handleCallback(Handler.java:873)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:193)
at android.os.HandlerThread.run(HandlerThread.java:65)
at com.android.server.ServiceThread.run(ServiceThread.java:44)
asked Jan 3 at 16:07
Psest328Psest328
3,16453463
I've searched this log but everything I've seen just says it's a warning. For some background, this does NOT crash on Oreo, but it DOES crash on Pie. I have no idea what broadcast could be causing it.
I've put breakpoints at every place I call "sendBroadcast" and can confirm that the crash happens before any broadcast is sent from the app.
if you require any code from any class, let me know and I'll put it up immediately
Any idea why this would be crashing on Pie?
2019-01-03 09:18:09.043 879-1094/? W/ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1023 com.android.server.am.AppStateBroadcaster.broadcastAppState:125 com.android.server.am.AppStateBroadcaster.sendApplicationFocusGain:49 com.android.server.am.OnePlusAmUtil$OnePlusActivityManagerService$1.run:346 android.os.Handler.handleCallback:873
2019-01-03 09:18:09.043 879-6821/? I/ActivityManager: Process com.android.chrome:sandboxed_process0 (pid 31022) has died: fore SVC
2019-01-03 09:18:09.043 1959-1959/? D/QcrilMsgTunnelIfaceManager: handleMessage what = 1
2019-01-03 09:18:09.043 1801-1801/? I/Zygote: Process 31022 exited cleanly (0)
2019-01-03 09:18:09.046 1959-1959/? I/QcrilOemhookMsgTunnel: [0]invokeOemRilRequestRaw: serial=4446 length=24
2019-01-03 09:18:09.047 879-1094/? E/ActivityManager: Sending non-protected broadcast diagandroid.app.ApplicationState from system 879:system/1000 pkg android
java.lang.Throwable
at com.android.server.am.ActivityManagerService.checkBroadcastFromSystem(ActivityManagerService.java:23205)
at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:23790)
at com.android.server.am.ActivityManagerService.broadcastIntent(ActivityManagerService.java:24025)
at android.app.ContextImpl.sendBroadcast(ContextImpl.java:1029)
at com.android.server.am.AppStateBroadcaster.broadcastAppState(AppStateBroadcaster.java:125)
at com.android.server.am.AppStateBroadcaster.sendApplicationFocusGain(AppStateBroadcaster.java:49)
at com.android.server.am.OnePlusAmUtil$OnePlusActivityManagerService$1.run(OnePlusAmUtil.java:346)
at android.os.Handler.handleCallback(Handler.java:873)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:193)
at android.os.HandlerThread.run(HandlerThread.java:65)
at com.android.server.ServiceThread.run(ServiceThread.java:44)
asked Jan 3 at 16:07
Psest328Psest328
3,16453463
asked Jan 3 at 16:07
Psest328Psest328
3,16453463
asked Jan 3 at 16:07
Psest328Psest328
3,16453463
asked Jan 3 at 16:07
Psest328Psest328
3,16453463
asked Jan 3 at 16:07
Psest328Psest328
3,16453463
3,16453463
1
Look in your logs for "FATAL" instead, as this may just be a red herring. If your application is actually crashing, you should get a stack trace.
– kcoppock
Jan 3 at 16:11
1
you were right! in 300 lines there's 1 reference to fatal: java.lang.NoClassDefFoundError: Failed resolution of: Lorg/apache/http/message/BasicNameValuePair; A search on stackoverflow gives me the answer to that. Thank you so much. Put this as an answer so I can give you a check mark!
– Psest328
Jan 3 at 16:17
add a comment |
1
Look in your logs for "FATAL" instead, as this may just be a red herring. If your application is actually crashing, you should get a stack trace.
– kcoppock
Jan 3 at 16:11
1
you were right! in 300 lines there's 1 reference to fatal: java.lang.NoClassDefFoundError: Failed resolution of: Lorg/apache/http/message/BasicNameValuePair; A search on stackoverflow gives me the answer to that. Thank you so much. Put this as an answer so I can give you a check mark!
– Psest328
Jan 3 at 16:17
1
1
Look in your logs for "FATAL" instead, as this may just be a red herring. If your application is actually crashing, you should get a stack trace.
– kcoppock
Jan 3 at 16:11
Look in your logs for "FATAL" instead, as this may just be a red herring. If your application is actually crashing, you should get a stack trace.
– kcoppock
Jan 3 at 16:11
1
1
you were right! in 300 lines there's 1 reference to fatal: java.lang.NoClassDefFoundError: Failed resolution of: Lorg/apache/http/message/BasicNameValuePair; A search on stackoverflow gives me the answer to that. Thank you so much. Put this as an answer so I can give you a check mark!
– Psest328
Jan 3 at 16:17
you were right! in 300 lines there's 1 reference to fatal: java.lang.NoClassDefFoundError: Failed resolution of: Lorg/apache/http/message/BasicNameValuePair; A search on stackoverflow gives me the answer to that. Thank you so much. Put this as an answer so I can give you a check mark!
– Psest328
Jan 3 at 16:17
add a comment |
1 Answer
1
active
oldest
votes
1
Occasionally you'll see stack traces printed in Logcat that are unrelated to your application. To find out what specifically is causing your crash, do a search for the word "FATAL". This will typically lead you to the actual cause of your application crash.
answered Jan 3 at 16:18
kcoppockkcoppock
115k39226245
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54025905%2fcrash-sending-non-protected-broadcast%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
1
Occasionally you'll see stack traces printed in Logcat that are unrelated to your application. To find out what specifically is causing your crash, do a search for the word "FATAL". This will typically lead you to the actual cause of your application crash.
answered Jan 3 at 16:18
kcoppockkcoppock
115k39226245
add a comment |
1
Occasionally you'll see stack traces printed in Logcat that are unrelated to your application. To find out what specifically is causing your crash, do a search for the word "FATAL". This will typically lead you to the actual cause of your application crash.
answered Jan 3 at 16:18
kcoppockkcoppock
115k39226245
add a comment |
1
1
1
Occasionally you'll see stack traces printed in Logcat that are unrelated to your application. To find out what specifically is causing your crash, do a search for the word "FATAL". This will typically lead you to the actual cause of your application crash.
answered Jan 3 at 16:18
kcoppockkcoppock
115k39226245
Occasionally you'll see stack traces printed in Logcat that are unrelated to your application. To find out what specifically is causing your crash, do a search for the word "FATAL". This will typically lead you to the actual cause of your application crash.
answered Jan 3 at 16:18
kcoppockkcoppock
115k39226245
answered Jan 3 at 16:18
kcoppockkcoppock
115k39226245
answered Jan 3 at 16:18
kcoppockkcoppock
115k39226245
answered Jan 3 at 16:18
kcoppockkcoppock
115k39226245
115k39226245
add a comment |
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54025905%2fcrash-sending-non-protected-broadcast%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Look in your logs for "FATAL" instead, as this may just be a red herring. If your application is actually crashing, you should get a stack trace.
– kcoppock
Jan 3 at 16:11
1
you were right! in 300 lines there's 1 reference to fatal: java.lang.NoClassDefFoundError: Failed resolution of: Lorg/apache/http/message/BasicNameValuePair; A search on stackoverflow gives me the answer to that. Thank you so much. Put this as an answer so I can give you a check mark!
– Psest328
Jan 3 at 16:17