acra

Add user input to ACRA crash report

半城伤御伤魂 提交于 2019-12-11 12:32:39
问题 Basically, this is what I'm trying to accomplish and nothing I've tried seems to work. Whenever there's a crash, before the ACRA report is sent, I'd like to display an EditText in a Dialog or something which allows the user to describe exactly what she was doing when this happened and give me some extra context for debugging. I know I can add whatever custom field to my crash report I want using ACRA.getErrorReporter().putCustomData(), but the problem is figuring out a way to display a view

Compilation error after upgrading from ACRA 4.5 to ACRA 4.6

狂风中的少年 提交于 2019-12-10 15:38:47
问题 I upgraded the ACRA library used by my application from 4.5.0 to 4.6.0 but I am getting a compilation error for formKey which used to work with 4.5. Here is the declaration: @ReportsCrashes( formKey = "", formUri = "", socketTimeout = 10000, httpMethod = org.acra.sender.HttpSender.Method.POST, mode = ReportingInteractionMode.SILENT, resDialogText = R.string.crash_dialog_text, resDialogIcon = android.R.drawable.ic_dialog_info, resDialogTitle = R.string.crash_dialog_title,

Logcat empty using ACRA on device

泪湿孤枕 提交于 2019-12-08 18:00:50
问题 So I'm using ACRA 4.4.0 with all defaults, and my logcat field is empty. My app has the <uses-permission android:name="android.permission.READ_LOGS" /> permissions, which should at least give me my own app logs since Jelly Bean. Final note: READ_LOG permission is not granted to third-party apps anymore since Android 4.1 (JellyBean). Starting with this version, logcat provides only traces from your own app , without requiring a permission. JellyBean logcat logs are retrieved by ACRA starting

Android - sending data from acra to a php script

守給你的承諾、 提交于 2019-12-08 06:31:55
问题 I've been using acra in some of my apps and sending the data to Google Docs spread sheets, but I would like to switch to sending data to a mysql setup I have running on a server where I feel the data would be more secure. I can see how to send the data using the post method but I can't tell the naming conventions of the data so I can catch them with a php script. Does anybody know what the variable names are or where I can look at them so I know what to look for in my php? 回答1: If the acra

ACRA exception Can only use lower 16 bits for requestCode

荒凉一梦 提交于 2019-12-06 23:07:06
问题 My app uses ACRA for error reporting, and I've got a couple of reports from my device with the error: Can only use lower 16 bits for requestCode.. Google shows this error occurring when using startActivityForResult, but I've searched my code a few times and I"m not calling that anywhere. I'm pretty confused and am wondering how this is impacting users (interestingly enough, the Crash Reports beta doesn't show any errors at all). Anyone else run into this? java.lang.RuntimeException: Unable to

Cannot resolve method 'formKey' in ACRA 4.7.0

我的梦境 提交于 2019-12-06 01:54:22
i tried setting up acra for my android project today, but it didnt work. I followed the instructions, importet the acra lib in gradle (compile 'ch.acra:acra:4.7.0') Then i added this: @ReportsCrashes(formKey = "", mailTo = "mail@adress.com", mode = ReportingInteractionMode.NOTIFICATION) protected void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); ACRA.init(this.getApplication()); I get the error Cannot resolve method 'formKey' , but when deleting formkey from parameters, i get @ReportsCrashes not applicable to method I also tried @ReportsCrashes(formUri = "http:/

How to override settings of ACRA in Android

醉酒当歌 提交于 2019-12-05 15:29:49
on my Application-Class I defined a ACRA with these annotations @ReportsCrashes(formKey = "", mailTo = "my@email.de", mode = ReportingInteractionMode.DIALOG, //resToastText = R.string.crash_toast_text, // optional, displayed as soon as the crash occurs, before collecting data which can take a few seconds resDialogText = R.string.crash_dialog_text, resDialogIcon = android.R.drawable.ic_dialog_info, //optional. default is a warning sign resDialogTitle = R.string.crash_dialog_title, // optional. default is your application name resDialogCommentPrompt = R.string.crash_dialog_comment_prompt, //

Native code - how to get function call stack (backtrace) programmatically

为君一笑 提交于 2019-12-05 09:22:26
问题 I have C++ codebase running on Android, and want to have crash reports sent by users. I'm using ACRA library which works fine for Java code, but when something crashes in native code, I don't get enough information. Actually I'd like to receive stack trace of native function calls. I know crash info is printed into logcat after my process ends, and I can configure ACRA to read/send logcat. I've setup my code to detect native crash using signal handlers and calling back to Java for reporting

Unfortunately, MyApp has stopped - no error logs in logcat

百般思念 提交于 2019-12-05 03:19:31
Every once in a while I get: Unfortunately, MyApp has stopped. Problem is easy to solve if you have some logs , but in my case logcat has absolutely no message of error (it has normal messages published by my app and other exceptions are shown there but not this one which causes this app has stopped ). Is there any chance I can solve this problem? The good thing is I can quite easily reproduce it, thus I'm trying to put as many information I can to logcat and then investigate what happened. I have ACRA up and running (other exceptions are caught by it but not this app has stopped ). When it

How to send Android Crash report using ACRA

人盡茶涼 提交于 2019-12-02 21:23:13
Am trying to send crash report from my applicatio to my domain or Mail but failed still. To get the crash report in mail, I did @ReportsCrashes( formKey = "", mailTo = "abc@gmail.com" ) And the response is, Sending file 1372758321000-approved.stacktrace checkAndSendReports - finish To get the crash report in my domain, I did @ReportsCrashes( formKey = "", formUri = "http://www.abc.com/test1" ) And the response is, Sending file 1372856882000-approved.stacktrace Failed to send crash report for 1372856882000-approved.stacktrace org.acra.sender.ReportSenderException: Error while sending FORM