gpt4 book ai didi

android - 无法为广播 Intent : process is bad 启动应用程序 com.bell.ship 的时钟/10024

转载 作者:行者123 更新时间:2023-11-29 00:44:42 24 4
gpt4 key购买 nike

我已经创建了类似警报通知的应用程序,所有这些都立即正常工作,但过了一段时间我发现了这样的错误无法启动应用程序 com.bell.ship 的时钟/10024 用于广播 Intent:logcat 中的进程错误。

logcat 如下所示。

08-10 19:00:24.350: DEBUG/dalvikvm(657): GC freed 2898 objects / 149328 bytes in 205ms
08-10 19:00:24.980: INFO/ActivityManager(64): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.bell.shipclock/.SplashScreen bnds=[3,138][77,217] }
08-10 19:00:25.970: INFO/ActivityManager(64): Displayed activity com.bell.shipclock/.SplashScreen: 833 ms (total 833 ms)
08-10 19:00:31.261: DEBUG/dalvikvm(142): GC freed 114 objects / 5248 bytes in 215ms
08-10 19:00:33.511: INFO/ActivityManager(64): Starting activity: Intent { cmp=com.bell.shipclock/.Home }
08-10 19:00:33.551: WARN/ActivityManager(64): Duplicate finish request for HistoryRecord{44da36f0 com.bell.shipclock/.SplashScreen}
08-10 19:00:34.631: INFO/ActivityManager(64): Displayed activity com.bell.shipclock/.Home: 1043 ms (total 1043 ms)
08-10 19:00:35.000: WARN/ActivityManager(64): Unable to launch app com.bell.shipclock/10024 for broadcast Intent { flg=0x4 cmp=com.bell.shipclock/.AlarmReceive1 (has extras) }: process is bad
08-10 19:00:35.011: WARN/ActivityManager(64): finishReceiver called but none active
08-10 19:01:35.011: WARN/ActivityManager(64): Unable to launch app com.bell.shipclock/10024 for broadcast Intent { flg=0x4 cmp=com.bell.shipclock/.AlarmReceive1 (has extras) }: process is bad
08-10 19:01:35.031: WARN/ActivityManager(64): finishReceiver called but none active
08-10 19:02:35.071: WARN/ActivityManager(64): Unable to launch app com.bell.shipclock/10024 for broadcast Intent { flg=0x4 cmp=com.bell.shipclock/.AlarmReceive1 (has extras) }: process is bad
08-10 19:02:35.121: WARN/ActivityManager(64): finishReceiver called but none active
08-10 19:03:35.060: WARN/ActivityManager(64): Unable to launch app com.bell.shipclock/10024 for broadcast Intent { flg=0x4 cmp=com.bell.shipclock/.AlarmReceive1 (has extras) }: process is bad
08-10 19:03:35.070: WARN/ActivityManager(64): finishReceiver called but none active
08-10 19:04:35.021: WARN/ActivityManager(64): Unable to launch app com.bell.shipclock/10024 for broadcast Intent { flg=0x4 cmp=com.bell.shipclock/.AlarmReceive1 (has extras) }: process is bad
08-10 19:04:35.031: WARN/ActivityManager(64): finishReceiver called but none active
08-10 19:05:27.730: DEBUG/dalvikvm(657): GC freed 8964 objects / 439224 bytes in 260ms
08-10 19:05:35.010: WARN/ActivityManager(64): Unable to launch app com.bell.shipclock/10024 for broadcast Intent { flg=0x4 cmp=com.bell.shipclock/.AlarmReceive1 (has extras) }: process is bad
08-10 19:05:35.023: WARN/ActivityManager(64): finishReceiver called but none active
08-10 19:06:35.051: WARN/ActivityManager(64): Unable to launch app com.bell.shipclock/10024 for broadcast Intent { flg=0x4 cmp=com.bell.shipclock/.AlarmReceive1 (has extras) }: process is bad
08-10 19:06:35.061: WARN/ActivityManager(64): finishReceiver called but none active
08-10 19:07:35.050: WARN/ActivityManager(64): Unable to launch app com.bell.shipclock/10024 for broadcast Intent { flg=0x4 cmp=com.bell.shipclock/.AlarmReceive1 (has extras) }: process is bad
08-10 19:07:35.061: WARN/ActivityManager(64): finishReceiver called but none active
08-10 19:08:35.035: WARN/ActivityManager(64): Unable to launch app com.bell.shipclock/10024 for broadcast Intent { flg=0x4 cmp=com.bell.shipclock/.AlarmReceive1 (has extras) }: process is bad
08-10 19:08:35.053: WARN/ActivityManager(64): finishReceiver called but none active
08-10 19:09:35.071: WARN/ActivityManager(64): Unable to launch app com.bell.shipclock/10024 for broadcast Intent { flg=0x4 cmp=com.bell.shipclock/.AlarmReceive1 (has extras) }: process is bad
08-10 19:09:35.090: WARN/ActivityManager(64): finishReceiver called but none active
08-10 19:10:34.050: DEBUG/dalvikvm(64): threadid=15: bogus mon 1+0>0; adjusting
08-10 19:10:35.050: WARN/ActivityManager(64): Unable to launch app com.bell.shipclock/10024 for broadcast Intent { flg=0x4 cmp=com.bell.shipclock/.AlarmReceive1 (has extras) }: process is bad
08-10 19:10:35.070: WARN/ActivityManager(64): finishReceiver called but none active
08-10 19:11:35.071: WARN/ActivityManager(64): Unable to launch app com.bell.shipclock/10024 for broadcast Intent { flg=0x4 cmp=com.bell.shipclock/.AlarmReceive1 (has extras) }: process is bad
08-10 19:11:35.090: WARN/ActivityManager(64): finishReceiver called but none active
08-10 19:12:15.870: DEBUG/dalvikvm(657): GC freed 12371 objects / 576528 bytes in 3495ms
08-10 19:12:17.961: DEBUG/dalvikvm(64): threadid=15: bogus mon 1+0>0; adjusting
08-10 19:12:35.011: WARN/ActivityManager(64): Unable to launch app com.bell.shipclock/10024 for broadcast Intent { flg=0x4 cmp=com.bell.shipclock/.AlarmReceive1 (has extras) }: process is bad
08-10 19:12:35.032: WARN/ActivityManager(64): finishReceiver called but none active
08-10 19:13:02.470: DEBUG/dalvikvm(64): GC freed 12863 objects / 648880 bytes in 2315ms
08-10 19:13:35.046: WARN/ActivityManager(64): Unable to launch app com.bell.shipclock/10024 for broadcast Intent { flg=0x4 cmp=com.bell.shipclock/.AlarmReceive1 (has extras) }: process is bad
08-10 19:13:35.061: WARN/ActivityManager(64): finishReceiver called but none active
08-10 19:14:35.081: WARN/ActivityManager(64): Unable to launch app com.bell.shipclock/10024 for broadcast Intent { flg=0x4 cmp=com.bell.shipclock/.AlarmReceive1 (has extras) }: process is bad
08-10 19:14:35.090: WARN/ActivityManager(64): finishReceiver called but none active

我是 Android 的新用户,我从来没有像以前那样看到过这个错误。

最佳答案

看起来您正在为初始屏幕调用 finish() 两次(“Duplicate finish request for HistoryRecord{44da36f0 com.bell.shipclock/.SplashScreen}”)。清除它,也许它会解决您的其他问题。

关于android - 无法为广播 Intent : process is bad 启动应用程序 com.bell.ship 的时钟/10024,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/7011871/

24 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com