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
Throwing retrofit2.HttpException HTTP 500 Internal Server Error, although exception is handled #3626
Comments
I have the same issue, any updates on this? |
Is this really a Retrofit2 problem or an internal FirebasePerf problem (I'm having the same issue) |
I have the same issue with no dependencies on Firebase. The issue is in okhttp: any status code != 200 throws an unhandled exception, causing a crash. Timeout also causes app crash. |
any update on this still having it ? |
I personally searched in my codebase and then found a code like this in a someCoroutineScope.launch {
// a retrofit call gets 4XX
} but it needs to have exception handlers: scope.launch(CoroutineExceptionHandler { _, ex -> logThisException(ex) }) {
// a retrofit call gets 4XX
} this is how i fixed for now. |
If I use that exception handler, I lose the original exception and get
I need to recover the original OkHttp exception, which has messages from the server |
Same issue here.. any one found any solution yet? |
Without a failing test case or minimally-reproducing sample project that demonstrates the problem it's impossible to know what's going on. I'll leave the issue open for 30 days in case someone wants to make one of those to aid us in debugging. |
I am using coroutines to call the api, If the response code is 500 then the app is crashing even though I'm catching the exception. Below is the implementation:
The text was updated successfully, but these errors were encountered: