Bangle.http timeout

[flaparoo]

Hi all

I've been getting timeout errors for HTTP requests (com.android.volley.TimeoutError), and I've tried to set the "timeout" option in the Bangle.http call - which didn't make a difference. There's still the same timeout (around 10sec).

Looking at the code, it seems that the "timeout" value is only used on the watch side (ie. in app/android/lib.js), however Gadgetbridge doesn't use it. I'm not well versed with Java, so my best interpretation is that Gadgetbridge uses the DefaultRetryPolicy (which I think would result in a 7.5sec timeout - incl. retry and "backoff").

Am I on the right track and Gadgetbridge should be modified to use the "timeout" value (incl. the default 30sec.)?
Or is something else involved which could cause the timeout?

[gfwilliams]

Hi - yes, perhaps you could pass the timeout to Gadgetbridge and have that change the HTTP request it makes - and then make the timeout on the Bangle side maybe 1 sec more than the requested timeout to give Gadgetbridge time to respond.

... but personally I'd be questioning why an HTTP request is taking over 7 seconds to complete? Even on a low bandwidth mobile connection that seems quite excessive

[flaparoo]

Fair point - it's worth getting in touch with the API operator.. It's a free API, so I can't be too demanding...

Nonetheless, I will try to submit a patch for Gadgetbridge (or open an issue if it exceeds my Java skills) to use the "timeout" value. At the moment, it's not behaving as expected / documented (the default timeout is NOT 30 sec.). And for my use-case, I would prefer to still get a response even if it takes up to 30 sec. - rather than an error.

Cheers!