BLE_HOST_TIMEOUT - intermittent issue with MakeWebRequest

Something has changed in last SDK/CIQ  Do you call webReq few times before revive data?

Hi, and thanks for responding. On my watch face, I call webreq only once per five minutes, and from my activity app only once per minute. In the activity app I get the call-back from the webreq (after a pretty long time), with responseCode = -2 (BLE_HOST_TIMEOUT) and no data.

with the watch face, the call-back function never triggers, probably the background process timed out before the makewebrequest returned with BLE host timed out. 

The only way to resolve is to go in to the Garmin connect app, or restart it. Then the watch synchronizes with Garmin Connect and the BLE connection appears to get re-initialized. I never get a bluetooth error, the BT connection is fine, but there seems to be some issue with the BLE "bridge". 

Perhaps there are two issues here:

First, something is really not working well with BLE through Garmin Connect, and this problem started just before or during summer. Probably related to a GC or iOS update. The GC team needs to fix this, the problem is that I really don't know how to reach them.

Second: it is not ideal that makewebrequest never calls the call-back function. The background process should perhaps not time out before the makewebrequest responds back. This creates loads of problems with my apps that use webreq in the background.       

This could have nothing to do with CIQ.  I ran into a case just a week or so back where there were issues with both my ISP and the server where I was getting odd errors.  Since then all my apps that do make web requests have been fine

Hi Jim, there is no issue with my ISP nor the web server (it's my web server). Those were my first thoughts. The problem always resolves as soon as I go into GC, immediately. The issue is clearly with the BLE connection between the device (Im testing on a Fenix5) and the mobile (testing on iOS)

well, it could be something else on the mobile that disturbs the connection, but nothing that I can think of. Again, the problem always goes away as soon as i open GC. 

The times I see -2 are when I'm at a borderline BT range between the Garmin and my Phone.  Anything change as far as your garmin's FW (like a BLE update)?  I run a WF with a background service to get weather data that I've run for weeks without issue (except the one I mentioned with my ISP/Data provider)

Thanks for replying Jim. I should perhaps try to test with another mobile and another watch, to see if the issue is with my mobile or watch. However, I do get a lot of support requests from people with similar problems but its hard to know if its the exact same issue. Since I don't get any response back on my webrequest (background times out before webrequest times out) its hard to catch the error and display some informative error message 

I can't recall the last time I got a support request like yours for any of my apps that do makeWebRequest calls.  I use Android, but I doubt that's the case with all the users.

okey. I will try to test with another iOS mobile and another watch, to see if its device/mobile specific. 

Fsallstrom Have you had any success testing with other devices? I'm not aware of any reports of this recently, but based on what you're describing, it sounds to me like a potential Garmin Connect Mobile issue (aside from the case where the device and the phone are too far apart to maintain a BLE connection).

I'm also curious whether the complaints you've received from users are limited to a specific device or set of devices.