search

kingrukawa / acra

Automatically exported from code.google.com/p/acra
0 stars 0 forks source link

ACRA SocketTimeoutException #45

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. A crash occurs.
2. An Acra notification is shown to the user (looking at the logcat a socket 
timeout exception is thrown after Acra reports the error)
3. Every time the app is started a crash report (for a socket timeout 
exception) is shown.

What is the expected output? What do you see instead?
Acra shouldn't notify the user for crashes/exceptions that are thrown in the 
background by Acra itself.

What version of the product are you using? On what operating system?
acra-3.1.1

Please provide any additional information below.

W/System.err( 1598): java.net.SocketTimeoutException
W/System.err( 1598):    at 
org.apache.harmony.luni.net.PlainSocketImpl.read(PlainSocketImpl.java:461)
W/System.err( 1598):    at 
org.apache.harmony.luni.net.SocketInputStream.read(SocketInputStream.java:85)
W/System.err( 1598):    at 
org.apache.harmony.luni.net.SocketInputStream.read(SocketInputStream.java:65)
W/System.err( 1598):    at 
java.io.BufferedInputStream.fillbuf(BufferedInputStream.java:140)
W/System.err( 1598):    at 
java.io.BufferedInputStream.read(BufferedInputStream.java:225)
W/System.err( 1598):    at 
org.apache.harmony.luni.internal.net.www.protocol.http.HttpURLConnectionImpl.rea
dLine(HttpURLConnectionImpl.java:660)
W/System.err( 1598):    at 
org.apache.harmony.luni.internal.net.www.protocol.http.HttpURLConnectionImpl.rea
dResponseHeaders(HttpURLConnectionImpl.java:690)
W/System.err( 1598):    at 
org.apache.harmony.luni.internal.net.www.protocol.http.HttpURLConnectionImpl.ret
rieveResponse(HttpURLConnectionImpl.java:1040)
W/System.err( 1598):    at 
org.apache.harmony.luni.internal.net.www.protocol.http.HttpURLConnectionImpl.get
InputStream(HttpURLConnectionImpl.java:510)
W/System.err( 1598):    at org.acra.HttpUtils.doPost(HttpUtils.java:95)
W/System.err( 1598):    at 
org.acra.ErrorReporter.sendCrashReport(ErrorReporter.java:655)
W/System.err( 1598):    at 
org.acra.ErrorReporter.checkAndSendReports(ErrorReporter.java:759)
W/System.err( 1598):    at 
org.acra.ErrorReporter$ReportsSenderWorker.run(ErrorReporter.java:109)

Original issue reported on code.google.com by stef...@qype.com on 30 Mar 2011 at 9:30

GoogleCodeExporter commented 8 years ago 
The SocketTimeoutException does not trigger new notifications about itself. In 
current stable versions of ACRA, with NOTIFICATION mode, a pending report 
always triggers an error notification until the report is actually sent or 
discarded by selecting OK or Cancel in the dialog.

If the user ignores the notification, ACRA keeps reminding him that there is a 
report pending. I agree this is not a nice behavior, this has been discussed in 
Issue 25 and will change in the next version of ACRA.

Original comment by kevin.gaudin on 4 Apr 2011 at 9:28

GoogleCodeExporter commented 8 years ago 
Thanks for your reply. Just one clarification though: by "NOTIFICATION mode" do 
you mean ReportingInteractionMode.NOTIFICATION? Because if that's the case, the 
same issue is there for ReportingInteractionMode.TOAST (the one we currently 
use), so a toast is shown every time the application is created.

Original comment by stef...@qype.com on 5 Apr 2011 at 7:33

GoogleCodeExporter commented 8 years ago 
Well, this is annoying.

I'm not decided between working on a hotfix for acra 3.1 or focusing on 
publishing acra 3.2 beta as soon as possible (like next week).

Kevin

Original comment by kevin.gaudin on 5 Apr 2011 at 7:50