App crashed when launched with following error
up vote
-1
down vote
favorite
2018-11-10 10:40:41.049 589-653/? E/ANDR-PERF-MPCTL: Invalid profile
no. 0, total profiles 0 only
2018-11-10 10:40:41.051 1593-2099/? E/ActivityTrigger:
activityStartTrigger: not
whiteListedcom.shl.h2/com.shl.h2.activities.LoginUI/2
2018-11-10 10:40:41.053 1593-2099/? E/ActivityTrigger:
activityResumeTrigger: not
whiteListedcom.shl.h2/com.shl.h2.activities.LoginUI/2
2018-11-10 10:40:41.114 1593-2099/? E/ActivityTrigger:
activityResumeTrigger: not
whiteListedcom.shl.h2/com.shl.h2.activities.LoginUI/2
2018-11-10 10:40:41.217 1593-2204/? E/ANDR-PERF-JNI:
com_qualcomm_qtiperformance_native_perf_io_prefetch_start
2018-11-10 10:40:41.222 1593-2204/? E/ActivityTrigger:
activityStartTrigger: not
whiteListedcom.google.android.packageinstaller/com.android.packageinstaller.permission.ui.GrantPermissionsActivity/27
2018-11-10 10:40:41.223 1593-2204/? E/ActivityTrigger:
activityResumeTrigger: not
whiteListedcom.google.android.packageinstaller/com.android.packageinstaller.permission.ui.GrantPermissionsActivity/27
2018-11-10 10:40:41.237 2120-25642/? E/NetworkScheduler: Invalid
component specified.
2018-11-10 10:40:41.250 1593-2099/? E/ActivityTrigger:
activityResumeTrigger: not
whiteListedcom.google.android.packageinstaller/com.android.packageinstaller.permission.ui.GrantPermissionsActivity/27
2018-11-10 10:40:41.289 1593-3098/? E/ActivityTrigger:
activityResumeTrigger: not
whiteListedcom.miui.home/com.miui.home.launcher.Launcher/4053012
2018-11-10 10:40:41.354 585-2093/? E/IzatSvc_ComboNetworkProvider:
Exiting with error proc line 208 "1"
android edited Nov 10 at 11:13
Ali Ahmed
1,1521214
asked Nov 10 at 4:34
Bellal Hossain
93
add a comment |
up vote
-1
down vote
favorite
2018-11-10 10:40:41.049 589-653/? E/ANDR-PERF-MPCTL: Invalid profile
no. 0, total profiles 0 only
2018-11-10 10:40:41.051 1593-2099/? E/ActivityTrigger:
activityStartTrigger: not
whiteListedcom.shl.h2/com.shl.h2.activities.LoginUI/2
2018-11-10 10:40:41.053 1593-2099/? E/ActivityTrigger:
activityResumeTrigger: not
whiteListedcom.shl.h2/com.shl.h2.activities.LoginUI/2
2018-11-10 10:40:41.114 1593-2099/? E/ActivityTrigger:
activityResumeTrigger: not
whiteListedcom.shl.h2/com.shl.h2.activities.LoginUI/2
2018-11-10 10:40:41.217 1593-2204/? E/ANDR-PERF-JNI:
com_qualcomm_qtiperformance_native_perf_io_prefetch_start
2018-11-10 10:40:41.222 1593-2204/? E/ActivityTrigger:
activityStartTrigger: not
whiteListedcom.google.android.packageinstaller/com.android.packageinstaller.permission.ui.GrantPermissionsActivity/27
2018-11-10 10:40:41.223 1593-2204/? E/ActivityTrigger:
activityResumeTrigger: not
whiteListedcom.google.android.packageinstaller/com.android.packageinstaller.permission.ui.GrantPermissionsActivity/27
2018-11-10 10:40:41.237 2120-25642/? E/NetworkScheduler: Invalid
component specified.
2018-11-10 10:40:41.250 1593-2099/? E/ActivityTrigger:
activityResumeTrigger: not
whiteListedcom.google.android.packageinstaller/com.android.packageinstaller.permission.ui.GrantPermissionsActivity/27
2018-11-10 10:40:41.289 1593-3098/? E/ActivityTrigger:
activityResumeTrigger: not
whiteListedcom.miui.home/com.miui.home.launcher.Launcher/4053012
2018-11-10 10:40:41.354 585-2093/? E/IzatSvc_ComboNetworkProvider:
Exiting with error proc line 208 "1"
android edited Nov 10 at 11:13
Ali Ahmed
1,1521214
asked Nov 10 at 4:34
Bellal Hossain
93
1
Those logs are likely unrelated to your crash. You're looking for the stack trace from your crash, which should be a large section of red lines.
– Mike M.
Nov 10 at 4:37
Still not it. The section you want should start withFATAL EXCEPTION, and have one of moreCaused by:subsections afterward. Please have a look at the answers on the question I linked above. Several have examples and screenshots that might help you find it.
– Mike M.
Nov 10 at 4:52
Click onLogcatthat you can see at lower left side of Android studio window. There you can see the exact crash report mentioned by Mike
– Karthic Srinivasan
Nov 10 at 6:17
@AliAhmed Please do not put logs in quote blocks. They need to be in code blocks.
– Mike M.
Nov 10 at 11:55
add a comment |
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
2018-11-10 10:40:41.049 589-653/? E/ANDR-PERF-MPCTL: Invalid profile
no. 0, total profiles 0 only
2018-11-10 10:40:41.051 1593-2099/? E/ActivityTrigger:
activityStartTrigger: not
whiteListedcom.shl.h2/com.shl.h2.activities.LoginUI/2
2018-11-10 10:40:41.053 1593-2099/? E/ActivityTrigger:
activityResumeTrigger: not
whiteListedcom.shl.h2/com.shl.h2.activities.LoginUI/2
2018-11-10 10:40:41.114 1593-2099/? E/ActivityTrigger:
activityResumeTrigger: not
whiteListedcom.shl.h2/com.shl.h2.activities.LoginUI/2
2018-11-10 10:40:41.217 1593-2204/? E/ANDR-PERF-JNI:
com_qualcomm_qtiperformance_native_perf_io_prefetch_start
2018-11-10 10:40:41.222 1593-2204/? E/ActivityTrigger:
activityStartTrigger: not
whiteListedcom.google.android.packageinstaller/com.android.packageinstaller.permission.ui.GrantPermissionsActivity/27
2018-11-10 10:40:41.223 1593-2204/? E/ActivityTrigger:
activityResumeTrigger: not
whiteListedcom.google.android.packageinstaller/com.android.packageinstaller.permission.ui.GrantPermissionsActivity/27
2018-11-10 10:40:41.237 2120-25642/? E/NetworkScheduler: Invalid
component specified.
2018-11-10 10:40:41.250 1593-2099/? E/ActivityTrigger:
activityResumeTrigger: not
whiteListedcom.google.android.packageinstaller/com.android.packageinstaller.permission.ui.GrantPermissionsActivity/27
2018-11-10 10:40:41.289 1593-3098/? E/ActivityTrigger:
activityResumeTrigger: not
whiteListedcom.miui.home/com.miui.home.launcher.Launcher/4053012
2018-11-10 10:40:41.354 585-2093/? E/IzatSvc_ComboNetworkProvider:
Exiting with error proc line 208 "1"
android edited Nov 10 at 11:13
Ali Ahmed
1,1521214
asked Nov 10 at 4:34
Bellal Hossain
93
2018-11-10 10:40:41.049 589-653/? E/ANDR-PERF-MPCTL: Invalid profile
no. 0, total profiles 0 only
2018-11-10 10:40:41.051 1593-2099/? E/ActivityTrigger:
activityStartTrigger: not
whiteListedcom.shl.h2/com.shl.h2.activities.LoginUI/2
2018-11-10 10:40:41.053 1593-2099/? E/ActivityTrigger:
activityResumeTrigger: not
whiteListedcom.shl.h2/com.shl.h2.activities.LoginUI/2
2018-11-10 10:40:41.114 1593-2099/? E/ActivityTrigger:
activityResumeTrigger: not
whiteListedcom.shl.h2/com.shl.h2.activities.LoginUI/2
2018-11-10 10:40:41.217 1593-2204/? E/ANDR-PERF-JNI:
com_qualcomm_qtiperformance_native_perf_io_prefetch_start
2018-11-10 10:40:41.222 1593-2204/? E/ActivityTrigger:
activityStartTrigger: not
whiteListedcom.google.android.packageinstaller/com.android.packageinstaller.permission.ui.GrantPermissionsActivity/27
2018-11-10 10:40:41.223 1593-2204/? E/ActivityTrigger:
activityResumeTrigger: not
whiteListedcom.google.android.packageinstaller/com.android.packageinstaller.permission.ui.GrantPermissionsActivity/27
2018-11-10 10:40:41.237 2120-25642/? E/NetworkScheduler: Invalid
component specified.
2018-11-10 10:40:41.250 1593-2099/? E/ActivityTrigger:
activityResumeTrigger: not
whiteListedcom.google.android.packageinstaller/com.android.packageinstaller.permission.ui.GrantPermissionsActivity/27
2018-11-10 10:40:41.289 1593-3098/? E/ActivityTrigger:
activityResumeTrigger: not
whiteListedcom.miui.home/com.miui.home.launcher.Launcher/4053012
2018-11-10 10:40:41.354 585-2093/? E/IzatSvc_ComboNetworkProvider:
Exiting with error proc line 208 "1"
android android edited Nov 10 at 11:13
Ali Ahmed
1,1521214
asked Nov 10 at 4:34
Bellal Hossain
93
edited Nov 10 at 11:13
Ali Ahmed
1,1521214
asked Nov 10 at 4:34
Bellal Hossain
93
edited Nov 10 at 11:13
Ali Ahmed
1,1521214
edited Nov 10 at 11:13
Ali Ahmed
1,1521214
edited Nov 10 at 11:13
Ali Ahmed
1,1521214
1,1521214
asked Nov 10 at 4:34
Bellal Hossain
93
asked Nov 10 at 4:34
Bellal Hossain
93
asked Nov 10 at 4:34
Bellal Hossain
93
93
1
Those logs are likely unrelated to your crash. You're looking for the stack trace from your crash, which should be a large section of red lines.
– Mike M.
Nov 10 at 4:37
Still not it. The section you want should start withFATAL EXCEPTION, and have one of moreCaused by:subsections afterward. Please have a look at the answers on the question I linked above. Several have examples and screenshots that might help you find it.
– Mike M.
Nov 10 at 4:52
Click onLogcatthat you can see at lower left side of Android studio window. There you can see the exact crash report mentioned by Mike
– Karthic Srinivasan
Nov 10 at 6:17
@AliAhmed Please do not put logs in quote blocks. They need to be in code blocks.
– Mike M.
Nov 10 at 11:55
add a comment |
1
Those logs are likely unrelated to your crash. You're looking for the stack trace from your crash, which should be a large section of red lines.
– Mike M.
Nov 10 at 4:37
Still not it. The section you want should start withFATAL EXCEPTION, and have one of moreCaused by:subsections afterward. Please have a look at the answers on the question I linked above. Several have examples and screenshots that might help you find it.
– Mike M.
Nov 10 at 4:52
Click onLogcatthat you can see at lower left side of Android studio window. There you can see the exact crash report mentioned by Mike
– Karthic Srinivasan
Nov 10 at 6:17
@AliAhmed Please do not put logs in quote blocks. They need to be in code blocks.
– Mike M.
Nov 10 at 11:55
1
1
Those logs are likely unrelated to your crash. You're looking for the stack trace from your crash, which should be a large section of red lines.
– Mike M.
Nov 10 at 4:37
Those logs are likely unrelated to your crash. You're looking for the stack trace from your crash, which should be a large section of red lines.
– Mike M.
Nov 10 at 4:37
Still not it. The section you want should start with
FATAL EXCEPTION, and have one of more Caused by: subsections afterward. Please have a look at the answers on the question I linked above. Several have examples and screenshots that might help you find it.– Mike M.
Nov 10 at 4:52
Still not it. The section you want should start with
FATAL EXCEPTION, and have one of more Caused by: subsections afterward. Please have a look at the answers on the question I linked above. Several have examples and screenshots that might help you find it.– Mike M.
Nov 10 at 4:52
Click on
Logcat that you can see at lower left side of Android studio window. There you can see the exact crash report mentioned by Mike– Karthic Srinivasan
Nov 10 at 6:17
Click on
Logcat that you can see at lower left side of Android studio window. There you can see the exact crash report mentioned by Mike– Karthic Srinivasan
Nov 10 at 6:17
@AliAhmed Please do not put logs in quote blocks. They need to be in code blocks.
– Mike M.
Nov 10 at 11:55
@AliAhmed Please do not put logs in quote blocks. They need to be in code blocks.
– Mike M.
Nov 10 at 11:55
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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.
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%2f53236022%2fapp-crashed-when-launched-with-following-error%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
Those logs are likely unrelated to your crash. You're looking for the stack trace from your crash, which should be a large section of red lines.
– Mike M.
Nov 10 at 4:37
Still not it. The section you want should start with
FATAL EXCEPTION, and have one of moreCaused by:subsections afterward. Please have a look at the answers on the question I linked above. Several have examples and screenshots that might help you find it.– Mike M.
Nov 10 at 4:52
Click on
Logcatthat you can see at lower left side of Android studio window. There you can see the exact crash report mentioned by Mike– Karthic Srinivasan
Nov 10 at 6:17
@AliAhmed Please do not put logs in quote blocks. They need to be in code blocks.
– Mike M.
Nov 10 at 11:55