-
Notifications
You must be signed in to change notification settings - Fork 1.1k
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
confirm success of upload #598
Comments
That option exists, if you are using dialog mode: use |
|
I've added toast options to version 5.0.0-alpha10: https://github.com/F43nd1r/acra/blob/modules/acra-core/src/main/java/org/acra/annotation/AcraCore.java#L415 As this is in alpha stage, the changes needed to use it are not well documented, but if you post your configuration here, I'll transform it. |
@F43nd1r glad to test as soon as I've worked through the current pile of hi-prio items, current config: @ReportsCrashes( |
@AcraCore(resReportSendSuccessToast = /*new string resource, optional*/,
resReportSendFailureToast = /*new string resource, optional*/)
@AcraHttpSender(
reportType = HttpSender.Type.JSON,
httpMethod = HttpSender.Method.POST,
uri = "http://acralyzer.vespucci.io/acraproxy")
@AcraDialog(
resText = R.string.crash_dialog_text,
resCommentPrompt = R.string.crash_dialog_comment_prompt,
resTheme = R.style.Theme_AppCompat_Light_Dialog) and these are the required dependencies: compile 'com.faendir.acra:acra-http:5.0.0-alpha11'
compile 'com.faendir.acra:acra-dialog:5.0.0-alpha11' |
@F43nd1r I've updated the dependency to 5.0.0 and changed the config, to
Which works fine, except that it doesn't actually display the toasts after successfully or unsuccessfully submitting a report. |
Can confirm this issue. Problem is the thread dies before the toast is sent.
|
Hopefully finally fixed in 5.0.2 |
it may be desirable to display toast confirming that report was successfully send (or that sending failed)
reported from downstream - MarcusWolschon/osmeditor4android#605 (comment)
The text was updated successfully, but these errors were encountered: