I have an app that is not in the market place (signed with a debug certificate), but would like to get crash log data, whenever my application crashes. Where can I find a log of why my app crashed?
我有一个不在市场上的应用程序(用调试证书签名),但是每当我的应用程序崩溃时,我希望得到崩溃日志数据。我在哪里可以找到我的应用崩溃的原因的日志?
14 个解决方案
#1
119
If your app is being downloaded by other people and crashing on remote devices, you may want to look into an Android error reporting library (referenced in this SO post). If it's just on your own local device, you can use LogCat.
Even if the device wasn't connected to a host machine when the crash occurred, connecting the device and issuing an adb logcat
command will download the entire logcat history (at least to the extent that it is buffered which is usually a loooot of log data, it's just not infinite). Do either of those options answer your question? If not can you attempt to clarify what you're looking for a bit more?
如果你的应用程序被其他人下载并在远程设备上崩溃,你可能需要查看Android错误报告库(在本文SO post中引用)。如果只是在本地设备上,可以使用LogCat。即使设备在崩溃发生时没有连接到主机,连接设备并发出adb logcat命令也会下载整个logcat历史记录(至少在它被缓存的程度上,这通常是大量的日志数据,它不是无限的)。这两个选项是否都能回答你的问题?如果没有,你能试着澄清你想要的更多一点吗?
#2
40
The way to do this is to implement the Thread.UncaughtExceptionHandler
interface and pass it to Thread.setDefaultUncaughtExceptionHandler()
at the beginning of your Activity's onCreate()
. Here is the implementation class TopExceptionHandler
.
这样做的方法是实现线程。UncaughtExceptionHandler接口,并在活动onCreate()的开头将其传递给Thread.setDefaultUncaughtExceptionHandler()。这是实现类TopExceptionHandler。
public class TopExceptionHandler implements Thread.UncaughtExceptionHandler {
private Thread.UncaughtExceptionHandler defaultUEH;
private Activity app = null;
public TopExceptionHandler(Activity app) {
this.defaultUEH = Thread.getDefaultUncaughtExceptionHandler();
this.app = app;
}
public void uncaughtException(Thread t, Throwable e) {
StackTraceElement[] arr = e.getStackTrace();
String report = e.toString()+"\n\n";
report += "--------- Stack trace ---------\n\n";
for (int i=0; i<arr.length; i++) {
report += " "+arr[i].toString()+"\n";
}
report += "-------------------------------\n\n";
// If the exception was thrown in a background thread inside
// AsyncTask, then the actual exception can be found with getCause
report += "--------- Cause ---------\n\n";
Throwable cause = e.getCause();
if(cause != null) {
report += cause.toString() + "\n\n";
arr = cause.getStackTrace();
for (int i=0; i<arr.length; i++) {
report += " "+arr[i].toString()+"\n";
}
}
report += "-------------------------------\n\n";
try {
FileOutputStream trace = app.openFileOutput("stack.trace",
Context.MODE_PRIVATE);
trace.write(report.getBytes());
trace.close();
} catch(IOException ioe) {
// ...
}
defaultUEH.uncaughtException(t, e);
}
}
Note We let the Android framework's defaultUEH to handle it.
注意,我们让Android框架的defaultUEH来处理它。
At the top of your Activity register an instance of above class like this:
在你的活动顶部注册一个以上类的实例,如:
@Override
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
Thread.setDefaultUncaughtExceptionHandler(new TopExceptionHandler(this));
...
This handler saves the trace in a file. When ReaderScope
restarts next time, it detects the file and prompts the user if he/she wants to email it to the developer.
此处理程序将跟踪保存在文件中。当ReaderScope下次重新启动时,它会检测到文件并提示用户,如果他/她想要将它发送给开发人员。
To Email the Stack Trace, execute following code to pack it in an email.
要发送堆栈跟踪,请执行以下代码,将其打包到电子邮件中。
try {
BufferedReader reader = new BufferedReader(
new InputStreamReader(ReaderScopeActivity.this.openFileInput("stack.trace")));
while((line = reader.readLine()) != null) {
trace += line+"\n";
}
} catch(FileNotFoundException fnfe) {
// ...
} catch(IOException ioe) {
// ...
}
Intent sendIntent = new Intent(Intent.ACTION_SEND);
String subject = "Error report";
String body = "Mail this to appdeveloper@gmail.com: " + "\n" + trace + "\n";
sendIntent.putExtra(Intent.EXTRA_EMAIL, new String[] {"readerscope@altcanvas.com"});
sendIntent.putExtra(Intent.EXTRA_TEXT, body);
sendIntent.putExtra(Intent.EXTRA_SUBJECT, subject);
sendIntent.setType("message/rfc822");
ReaderScopeActivity.this.startActivity(Intent.createChooser(sendIntent, "Title:"));
ReaderScopeActivity.this.deleteFile("stack.trace");
Or you can also use ACRA Error Reporting System.Just Include the ACRA.jar in your project libs and use the below code snippet before your launcher activity class declaration
或者您也可以使用ACRA错误报告系统。只包括肢端。在您的项目libs中,使用以下代码片段,在您的启动活动类声明之前。
@ReportsCrashes(formKey = "", mailTo = "abc@gmail.com;def@yahoo.com", mode = ReportingInteractionMode.SILENT)
#3
23
This is from http://www.herongyang.com/Android/Debug-adb-logcat-Command-Debugging.html
这是来自http://www.herongyang.com/Android/Debug-adb-logcat-Command-Debugging.html
You can use adb:
您可以使用adb:
adb logcat AndroidRuntime:E *:S
#4
12
You can use Apphance. This is a cross-platform service (now mainly Android, iOS with other platforms on their way) which allows to debug remotely any mobile device (Android, iOS now - others under development). It's much more than just a crashlog, in fact it is much more: logging, reporting of problems by testers, crashlogs. It takes about 5 minutes to integrate. Currently you can request for access to closed beta.
您可以使用Apphance。这是一个跨平台的服务(现在主要是Android, iOS和其他平台),可以远程调试任何移动设备(Android, iOS现在——其他正在开发的设备)。它不仅仅是一个日志记录,实际上它更多:日志记录、测试人员报告问题、日志记录。积分大约需要5分钟。目前,您可以请求访问封闭的beta。
Disclaimer: I am CTO of Polidea, a company behind Apphance and co-creator of it.
免责声明:我是Polidea公司的首席技术官,该公司是该公司的创始人和创始人之一。
Update: Apphance is no longer closed beta! Update 2: Apphance is available as part of http://applause.com offering
更新:升级不再是封闭的beta!更新2:Apphance是http://applause.com提供的一部分。
#5
11
You can try this from console:-
你可以从控制台试试这个:-
adb logcat -b crash
亚行logcat - b崩溃
#6
7
If you're using Eclipse, make sure you use debug and not run. Make sure you are in the debug perspective (top right) You may have to hit 'Resume' (F8) a few times for the log to print. The crash log will be in the Logcat window at the bottom- double click for fullscreen and make sure you scroll to the bottom. You'll see red text for errors, the crash trace will be something like
如果您正在使用Eclipse,请确保使用了debug而不是run。确保您处于debug透视图(右上角)中,您可能需要多次点击“Resume”(F8)才能打印日志。崩溃日志将在底部的Logcat窗口-双击全屏,确保你滚动到底部。您将看到错误的红色文本,崩溃跟踪将是类似的
09-04 21:35:15.228: ERROR/AndroidRuntime(778): Uncaught handler: thread main exiting due to uncaught exception
09-04 21:35:15.397: ERROR/AndroidRuntime(778): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.dazlious.android.helloworld/com.dazlious.android.helloworld.main}: java.lang.ArrayIndexOutOfBoundsException
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2268)
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2284)
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at android.app.ActivityThread.access$1800(ActivityThread.java:112)
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1692)
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at android.os.Handler.dispatchMessage(Handler.java:99)
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at android.os.Looper.loop(Looper.java:123)
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at android.app.ActivityThread.main(ActivityThread.java:3948)
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at java.lang.reflect.Method.invokeNative(Native Method)
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at java.lang.reflect.Method.invoke(Method.java:521)
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:782)
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:540)
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at dalvik.system.NativeStart.main(Native Method)
09-04 21:35:15.397: ERROR/AndroidRuntime(778): Caused by: java.lang.ArrayIndexOutOfBoundsException
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at com.example.android.helloworld.main.onCreate(main.java:13)
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1123)
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2231)
09-04 21:35:15.397: ERROR/AndroidRuntime(778): ... 11 more
The important parts for this one are
这个问题的重要部分是
09-04 21:35:15.397: ERROR/AndroidRuntime(778): Caused by: java.lang.ArrayIndexOutOfBoundsException
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at com.example.android.helloworld.main.onCreate(main.java:13)
those tell us it was an array out of bounds exception on on line 13 of main.java in the onCrate method.
它们告诉我们,在main的第13行,这是一个越界异常数组。在onCrate方法中的java。
#7
7
Here is another solution for Crash Log.
这是另一个崩溃日志的解决方案。
Android market has tool named "Crash Collector"
Android market有一个名为“崩溃收集器”的工具
check following link for more information
查看以下链接了解更多信息。
http://kpbird.blogspot.com/2011/08/android-application-crash-logs.html
http://kpbird.blogspot.com/2011/08/android-application-crash-logs.html
#8
4
You can use ACRA from this. Including this library to your projects and configuring it, you could receive (into your email or gdocs) their crash reports. Sorry for my bad English.
你可以用ACRA。将这个库包含到您的项目中并配置它,您可以(在您的电子邮件或gdocs中)接收它们的崩溃报告。对不起,我的英语不好。
#9
4
If you are looking for a basic crash reporting tool, try crashlytics.
如果您正在寻找一个基本的崩溃报告工具,请尝试崩溃学。
If you want a more advanced reporting tool, Checkout Gryphonet. It logs all the crashes occured along with the exact line of code that caused the crash along with automated markers that show you the steps the user took prior to the crash and more.
如果您想要一个更高级的报告工具,请签出Gryphonet。它记录了所有发生的崩溃,以及导致崩溃的代码行以及自动标记,这些标记显示了用户在崩溃之前所采取的步骤等等。
Good luck!
好运!
#12
0
If you're just looking for the crash log while your phone is connected to the computer, use the DDMS view in Eclipse and the report is right there in LogCat within DDMS when your app crashes while debugging.
如果您只是在手机连接到计算机时查找崩溃日志,请在Eclipse中使用DDMS视图,当应用程序在调试时崩溃时,报告就在DDMS中的LogCat中。
#13
0
I have created this library to solve all your problems. Crash Reporter is a handy tool to capture all your crashes and log them in device locally
我创建这个图书馆是为了解决你所有的问题。崩溃报告程序是一个方便的工具,用于捕获所有崩溃并在本地设备中进行日志记录
Just add this dependency and you're good to go.
只要添加这个依赖项就可以了。
compile 'com.balsikandar.android:crashreporter:1.0.1'
Find all your crashes in device locally and fix them at your convenience. Crashes are saved using date and time format easy to track. Plus it also provides API for capture Logged Exceptions using below method.
在本地找到你所有的设备崩溃,并在你方便的时候修复它们。使用易于跟踪的日期和时间格式保存崩溃。此外,它还提供了API,用于使用下面的方法捕获日志异常。
CrashRepoter.logException(Exception e)
#14
-1
Try Carsh log app from android.
试试android上的Carsh log应用。
use the link to download app.
使用该链接下载应用程序。
#1
119
If your app is being downloaded by other people and crashing on remote devices, you may want to look into an Android error reporting library (referenced in this SO post). If it's just on your own local device, you can use LogCat.
Even if the device wasn't connected to a host machine when the crash occurred, connecting the device and issuing an adb logcat
command will download the entire logcat history (at least to the extent that it is buffered which is usually a loooot of log data, it's just not infinite). Do either of those options answer your question? If not can you attempt to clarify what you're looking for a bit more?
如果你的应用程序被其他人下载并在远程设备上崩溃,你可能需要查看Android错误报告库(在本文SO post中引用)。如果只是在本地设备上,可以使用LogCat。即使设备在崩溃发生时没有连接到主机,连接设备并发出adb logcat命令也会下载整个logcat历史记录(至少在它被缓存的程度上,这通常是大量的日志数据,它不是无限的)。这两个选项是否都能回答你的问题?如果没有,你能试着澄清你想要的更多一点吗?
#2
40
The way to do this is to implement the Thread.UncaughtExceptionHandler
interface and pass it to Thread.setDefaultUncaughtExceptionHandler()
at the beginning of your Activity's onCreate()
. Here is the implementation class TopExceptionHandler
.
这样做的方法是实现线程。UncaughtExceptionHandler接口,并在活动onCreate()的开头将其传递给Thread.setDefaultUncaughtExceptionHandler()。这是实现类TopExceptionHandler。
public class TopExceptionHandler implements Thread.UncaughtExceptionHandler {
private Thread.UncaughtExceptionHandler defaultUEH;
private Activity app = null;
public TopExceptionHandler(Activity app) {
this.defaultUEH = Thread.getDefaultUncaughtExceptionHandler();
this.app = app;
}
public void uncaughtException(Thread t, Throwable e) {
StackTraceElement[] arr = e.getStackTrace();
String report = e.toString()+"\n\n";
report += "--------- Stack trace ---------\n\n";
for (int i=0; i<arr.length; i++) {
report += " "+arr[i].toString()+"\n";
}
report += "-------------------------------\n\n";
// If the exception was thrown in a background thread inside
// AsyncTask, then the actual exception can be found with getCause
report += "--------- Cause ---------\n\n";
Throwable cause = e.getCause();
if(cause != null) {
report += cause.toString() + "\n\n";
arr = cause.getStackTrace();
for (int i=0; i<arr.length; i++) {
report += " "+arr[i].toString()+"\n";
}
}
report += "-------------------------------\n\n";
try {
FileOutputStream trace = app.openFileOutput("stack.trace",
Context.MODE_PRIVATE);
trace.write(report.getBytes());
trace.close();
} catch(IOException ioe) {
// ...
}
defaultUEH.uncaughtException(t, e);
}
}
Note We let the Android framework's defaultUEH to handle it.
注意,我们让Android框架的defaultUEH来处理它。
At the top of your Activity register an instance of above class like this:
在你的活动顶部注册一个以上类的实例,如:
@Override
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
Thread.setDefaultUncaughtExceptionHandler(new TopExceptionHandler(this));
...
This handler saves the trace in a file. When ReaderScope
restarts next time, it detects the file and prompts the user if he/she wants to email it to the developer.
此处理程序将跟踪保存在文件中。当ReaderScope下次重新启动时,它会检测到文件并提示用户,如果他/她想要将它发送给开发人员。
To Email the Stack Trace, execute following code to pack it in an email.
要发送堆栈跟踪,请执行以下代码,将其打包到电子邮件中。
try {
BufferedReader reader = new BufferedReader(
new InputStreamReader(ReaderScopeActivity.this.openFileInput("stack.trace")));
while((line = reader.readLine()) != null) {
trace += line+"\n";
}
} catch(FileNotFoundException fnfe) {
// ...
} catch(IOException ioe) {
// ...
}
Intent sendIntent = new Intent(Intent.ACTION_SEND);
String subject = "Error report";
String body = "Mail this to appdeveloper@gmail.com: " + "\n" + trace + "\n";
sendIntent.putExtra(Intent.EXTRA_EMAIL, new String[] {"readerscope@altcanvas.com"});
sendIntent.putExtra(Intent.EXTRA_TEXT, body);
sendIntent.putExtra(Intent.EXTRA_SUBJECT, subject);
sendIntent.setType("message/rfc822");
ReaderScopeActivity.this.startActivity(Intent.createChooser(sendIntent, "Title:"));
ReaderScopeActivity.this.deleteFile("stack.trace");
Or you can also use ACRA Error Reporting System.Just Include the ACRA.jar in your project libs and use the below code snippet before your launcher activity class declaration
或者您也可以使用ACRA错误报告系统。只包括肢端。在您的项目libs中,使用以下代码片段,在您的启动活动类声明之前。
@ReportsCrashes(formKey = "", mailTo = "abc@gmail.com;def@yahoo.com", mode = ReportingInteractionMode.SILENT)
#3
23
This is from http://www.herongyang.com/Android/Debug-adb-logcat-Command-Debugging.html
这是来自http://www.herongyang.com/Android/Debug-adb-logcat-Command-Debugging.html
You can use adb:
您可以使用adb:
adb logcat AndroidRuntime:E *:S
#4
12
You can use Apphance. This is a cross-platform service (now mainly Android, iOS with other platforms on their way) which allows to debug remotely any mobile device (Android, iOS now - others under development). It's much more than just a crashlog, in fact it is much more: logging, reporting of problems by testers, crashlogs. It takes about 5 minutes to integrate. Currently you can request for access to closed beta.
您可以使用Apphance。这是一个跨平台的服务(现在主要是Android, iOS和其他平台),可以远程调试任何移动设备(Android, iOS现在——其他正在开发的设备)。它不仅仅是一个日志记录,实际上它更多:日志记录、测试人员报告问题、日志记录。积分大约需要5分钟。目前,您可以请求访问封闭的beta。
Disclaimer: I am CTO of Polidea, a company behind Apphance and co-creator of it.
免责声明:我是Polidea公司的首席技术官,该公司是该公司的创始人和创始人之一。
Update: Apphance is no longer closed beta! Update 2: Apphance is available as part of http://applause.com offering
更新:升级不再是封闭的beta!更新2:Apphance是http://applause.com提供的一部分。
#5
11
You can try this from console:-
你可以从控制台试试这个:-
adb logcat -b crash
亚行logcat - b崩溃
#6
7
If you're using Eclipse, make sure you use debug and not run. Make sure you are in the debug perspective (top right) You may have to hit 'Resume' (F8) a few times for the log to print. The crash log will be in the Logcat window at the bottom- double click for fullscreen and make sure you scroll to the bottom. You'll see red text for errors, the crash trace will be something like
如果您正在使用Eclipse,请确保使用了debug而不是run。确保您处于debug透视图(右上角)中,您可能需要多次点击“Resume”(F8)才能打印日志。崩溃日志将在底部的Logcat窗口-双击全屏,确保你滚动到底部。您将看到错误的红色文本,崩溃跟踪将是类似的
09-04 21:35:15.228: ERROR/AndroidRuntime(778): Uncaught handler: thread main exiting due to uncaught exception
09-04 21:35:15.397: ERROR/AndroidRuntime(778): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.dazlious.android.helloworld/com.dazlious.android.helloworld.main}: java.lang.ArrayIndexOutOfBoundsException
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2268)
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2284)
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at android.app.ActivityThread.access$1800(ActivityThread.java:112)
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1692)
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at android.os.Handler.dispatchMessage(Handler.java:99)
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at android.os.Looper.loop(Looper.java:123)
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at android.app.ActivityThread.main(ActivityThread.java:3948)
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at java.lang.reflect.Method.invokeNative(Native Method)
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at java.lang.reflect.Method.invoke(Method.java:521)
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:782)
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:540)
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at dalvik.system.NativeStart.main(Native Method)
09-04 21:35:15.397: ERROR/AndroidRuntime(778): Caused by: java.lang.ArrayIndexOutOfBoundsException
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at com.example.android.helloworld.main.onCreate(main.java:13)
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1123)
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2231)
09-04 21:35:15.397: ERROR/AndroidRuntime(778): ... 11 more
The important parts for this one are
这个问题的重要部分是
09-04 21:35:15.397: ERROR/AndroidRuntime(778): Caused by: java.lang.ArrayIndexOutOfBoundsException
09-04 21:35:15.397: ERROR/AndroidRuntime(778): at com.example.android.helloworld.main.onCreate(main.java:13)
those tell us it was an array out of bounds exception on on line 13 of main.java in the onCrate method.
它们告诉我们,在main的第13行,这是一个越界异常数组。在onCrate方法中的java。
#7
7
Here is another solution for Crash Log.
这是另一个崩溃日志的解决方案。
Android market has tool named "Crash Collector"
Android market有一个名为“崩溃收集器”的工具
check following link for more information
查看以下链接了解更多信息。
http://kpbird.blogspot.com/2011/08/android-application-crash-logs.html
http://kpbird.blogspot.com/2011/08/android-application-crash-logs.html
#8
4
You can use ACRA from this. Including this library to your projects and configuring it, you could receive (into your email or gdocs) their crash reports. Sorry for my bad English.
你可以用ACRA。将这个库包含到您的项目中并配置它,您可以(在您的电子邮件或gdocs中)接收它们的崩溃报告。对不起,我的英语不好。
#9
4
If you are looking for a basic crash reporting tool, try crashlytics.
如果您正在寻找一个基本的崩溃报告工具,请尝试崩溃学。
If you want a more advanced reporting tool, Checkout Gryphonet. It logs all the crashes occured along with the exact line of code that caused the crash along with automated markers that show you the steps the user took prior to the crash and more.
如果您想要一个更高级的报告工具,请签出Gryphonet。它记录了所有发生的崩溃,以及导致崩溃的代码行以及自动标记,这些标记显示了用户在崩溃之前所采取的步骤等等。
Good luck!
好运!
#10
#11
#12
0
If you're just looking for the crash log while your phone is connected to the computer, use the DDMS view in Eclipse and the report is right there in LogCat within DDMS when your app crashes while debugging.
如果您只是在手机连接到计算机时查找崩溃日志,请在Eclipse中使用DDMS视图,当应用程序在调试时崩溃时,报告就在DDMS中的LogCat中。
#13
0
I have created this library to solve all your problems. Crash Reporter is a handy tool to capture all your crashes and log them in device locally
我创建这个图书馆是为了解决你所有的问题。崩溃报告程序是一个方便的工具,用于捕获所有崩溃并在本地设备中进行日志记录
Just add this dependency and you're good to go.
只要添加这个依赖项就可以了。
compile 'com.balsikandar.android:crashreporter:1.0.1'
Find all your crashes in device locally and fix them at your convenience. Crashes are saved using date and time format easy to track. Plus it also provides API for capture Logged Exceptions using below method.
在本地找到你所有的设备崩溃,并在你方便的时候修复它们。使用易于跟踪的日期和时间格式保存崩溃。此外,它还提供了API,用于使用下面的方法捕获日志异常。
CrashRepoter.logException(Exception e)
#14
-1
Try Carsh log app from android.
试试android上的Carsh log应用。
use the link to download app.
使用该链接下载应用程序。