Add RecommendedServerIssue for connection problems about jellyfin-sdk-kotlin HOT 6 CLOSED

Yes. We have a lot of issue reports for our clients caused by SSL issues. Right no we don't detect those in the SDK which isn't helpful. I'd like to have a single RecommendedServerIssue for all SSL related issues with more detail in it's body (e.g. the exception that caused it, maybe an enum with the type of SSL error).

The NoConnection one is also still nice to have.

from jellyfin-sdk-kotlin.

Yes they should be separate, one for SSL related issues and one for no connection. Maybe name it something like "UnsupportedSSL"? Since it's not necessarily a bad connection.

from jellyfin-sdk-kotlin.

Hi! Is this issue still actual? I would like to work on this if you dont mind

from jellyfin-sdk-kotlin.

Ok. I will look into the code and familarize myself with the api client.

from jellyfin-sdk-kotlin.

Hi! What do you think of naming the new RecommentedServerIssue implementation for SSL Errors as BadConnection? IMO, NoConnection is a bit misleading.

BadConnection implies we reached the server but the server/client aborted the connection (e.g SSL configuration error or just a timeout).
NoConnection implies we didn't reach the server at all (e.g. Cannot resolve url).

Regardless of the naming -> I will try to map ssl errors thrown by OkHttp due to SSL and add that to the new implementation class.

from jellyfin-sdk-kotlin.

Hi! Sorry for the delay, I created a pull request with required feature. I'm still thinking on how to approach testing this...

from jellyfin-sdk-kotlin.