Socket Timeout since 2.4.0

[sjonez]

I sync with a shared ICS URL from Outlook 365 (https://outlook.office365.com/owa/calendar/...). I upgraded to 2.4.0 due to the recent requirement of a custom user-agent but now I'm seeing consistent socket timeout errors when I try to sync.

If I paste the ICS URL into a browser it consistently takes around 10-12 seconds before the download begins, so the slowness is on Microsoft's end, possibly due to the number of events and/or whatever it's doing to compile the ICS on the fly? (the ICS file is around 2MB). I only rarely saw sync failures in previous versions, so I'm not sure if the socket timeout has been shortened in this version?

[sunkup]

Not on purpose. But maybe the switch to ktor (this PR) did something ... @ArnyminerZ Do you have an idea?

[ArnyminerZ]

We have some timeouts set:

icsx5/app/src/main/java/at/bitfire/icsdroid/AppHttpClient.kt

Lines 63 to 69 in 576e861

	config {
	followRedirects(false)
	connectTimeout(20, TimeUnit.SECONDS)
	readTimeout(60, TimeUnit.SECONDS)
	sslSocketFactory(sslContext.socketFactory, certManager)
	hostnameVerifier(certManager.HostnameVerifier(OkHostnameVerifier))
	}

20 seconds to connect, and 60 seconds to read. It should be plenty, but I guess we can increase it?

[sjonez]

I don't think those timeouts are being used then, as I've just timed it and from clicking force sync to error is exactly 10 seconds

[sjonez]

if it helps, in the error message it says "Socket timeout has expired [url=https://..., socket_timeout=unknown]

[sunkup]

True. Tracked in: #684