2013-01-08 82 views
0

我無法準確識別錯誤。我的申請工作正常。但是我,當我通過活動的應用程序導航,我注意到在紅顏色,但應用程序日誌貓這些錯誤不會崩潰運行時日誌中的錯誤

01-08 07:13:09.363: E/StrictMode(1067):  at android.app.LoadedApk$ServiceDispatcher.<init>(LoadedApk.java:969) 
01-08 07:13:09.363: E/StrictMode(1067):  at android.app.LoadedApk.getServiceDispatcher(LoadedApk.java:863) 
01-08 07:13:09.363: E/StrictMode(1067):  at android.app.ContextImpl.bindService(ContextImpl.java:1418) 
01-08 07:13:09.363: E/StrictMode(1067):  at android.app.ContextImpl.bindService(ContextImpl.java:1407) 
01-08 07:13:09.363: E/StrictMode(1067):  at android.content.ContextWrapper.bindService(ContextWrapper.java:473) 
01-08 07:13:09.363: E/StrictMode(1067):  at com.android.emailcommon.service.ServiceProxy.setTask(ServiceProxy.java:157) 
01-08 07:13:09.363: E/StrictMode(1067):  at com.android.emailcommon.service.ServiceProxy.setTask(ServiceProxy.java:145) 
01-08 07:13:09.363: E/StrictMode(1067):  at com.android.emailcommon.service.AccountServiceProxy.getDeviceId(AccountServiceProxy.java:116) 
01-08 07:13:09.363: E/StrictMode(1067):  at com.android.exchange.ExchangeService.getDeviceId(ExchangeService.java:1249) 
01-08 07:13:09.363: E/StrictMode(1067):  at com.android.exchange.ExchangeService$7.run(ExchangeService.java:1856) 
01-08 07:13:09.363: E/StrictMode(1067):  at com.android.emailcommon.utility.Utility$2.doInBackground(Utility.java:551) 
01-08 07:13:09.363: E/StrictMode(1067):  at com.android.emailcommon.utility.Utility$2.doInBackground(Utility.java:549) 
01-08 07:13:09.363: E/StrictMode(1067):  at android.os.AsyncTask$2.call(AsyncTask.java:287) 
01-08 07:13:09.363: E/StrictMode(1067):  at java.util.concurrent.FutureTask.run(FutureTask.java:234) 
01-08 07:13:09.363: E/StrictMode(1067):  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1080) 
01-08 07:13:09.363: E/StrictMode(1067):  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:573) 
01-08 07:13:09.363: E/StrictMode(1067):  at java.lang.Thread.run(Thread.java:856) 
01-08 07:13:09.413: W/ActivityManager(755): Unbind failed: could not find connection for [email protected] 
01-08 07:13:09.413: W/Trace(1067): Unexpected value from nativeGetEnabledTags: 0 
01-08 07:13:09.413: W/Trace(1067): Unexpected value from nativeGetEnabledTags: 0 
01-08 07:13:23.563: W/Trace(1005): Unexpected value from nativeGetEnabledTags: 0 
01-08 07:13:23.573: W/Trace(1005): Unexpected value from nativeGetEnabledTags: 0 
01-08 07:13:54.157: D/ExchangeService(1067): Received deviceId from Email app: null 

任何人能解釋這是怎麼回事這裏

+0

我建議你添加一個過濾器你的'logcat',你的軟件包名稱是「應用程序名稱」。這樣您就可以更好地瞭解應用的輸出。 :) – ninetwozero

回答

1

您aapplication是不是因爲崩潰錯誤是E/StrictMode,當應用程序崩潰錯誤報告爲E/AndroidRuntime,似乎你已經在你的應用程序中啓用嚴格模式檢查,它報告可能的錯誤,並且可以更正

+0

是否意味着我不想擔心這個? – newday