Check bug reporting #343
Comments
probably related to the networking changes from #305… |
hm, debugging the ExceptionHandler.submitStackTraces() gives me a weird Exception trying to establish the connection: javax.net.ssl.SSLHandshakeException: Handshake failed Why is it using SSLv3 here? |
HTTP request seemed to work fine… |
when using OkHttp I'm getting:
|
SSLv3 is deactivated on the server. It should at least use TLSv1.0 Check https://www.ssllabs.com/ssltest/analyze.html?d=tumcabe.in.tum.de&latest The Reporter in ExceptionsHandler still uses HttpURLConnection. Was this broken maybe when you replaced it in #305? |
Can we somehow verify, that we now receive these bug reports? Plus we should somehow handle, that if the ExceptionHandler fails to submit the stacktraces, it tries to resubmit then. |
Yes, just add a debug function somewhere hidden in the menu of the TCA that divides by zero, which will crash the app and should trigger such a report. |
@pfent try to access the toString of a null object somewhere. On next startup the bugreport will be transmitted and should showup in the UI. Worked for me when I tested it. Yeah we could save the reports for later, we just need to make sure, that we don't flood the storage space with those reports. |
Since 1.3.X no bug reports were reported back to our system. Check why this happens and release fix asap.
The text was updated successfully, but these errors were encountered: