Help with cause of BLE_REQUEST_CANCELLED error

Hi,

I have some users of my app that are consistently getting BLE_REQUEST_CANCELLED (-5) errors for Communications.makeWebRequest calls.

The docs state that it's "The request was cancelled at the request of the system." but doesn't say why it might occur, is this the expected return code

for outstanding requests when a call to Communications.cancelAllRequests is made or does it indicate something else?

Thanks

Top Replies

flogazo over 4 years ago +1

Hi,

I get the same thing, also in a widget and only on the device (fr945) and NOT in the simulator.

I want to trigger my request when the widget is shown and subsequently whenever onSelect() happens.

…
6545774 over 4 years ago in reply to flogazo +1

In the end I did the web request 100ms after the view loaded with a timer, it was never something I could replicate in the simulator and not all models were affected (eg. my 645 music never had any issues…

All Replies

0 jim_m_58 over 5 years ago

I see this error every once in a while, and I think it may happen when the makeWebRequest has been done but the callback hasn't been called and the app shuts down. The callback is first called with this error,

0 4709404 over 5 years ago

Thanks Jim, that doesn't seem to be the case for me, I make a makeWebRequest call, get the -5 almost immediately while the widget is still running. Subsequent makeWebRequest calls seem to succeed.

At this point the only option I can think of is to add retries.

0 flogazo over 4 years ago

Hi,

I get the same thing, also in a widget and only on the device (fr945) and NOT in the simulator.

I want to trigger my request when the widget is shown and subsequently whenever onSelect() happens.

The onSelect() works fine every time, but the call from getInitialView() fails with "-5".
Is getInitialView() maybe to early and some resource needed for the request is not ready?

0 jim_m_58 over 4 years ago in reply to flogazo

When I trigger a makeWebRequest in a widget, I do it in initialize() for the view and never had much of an issue with being canceled. I do see it at times if I trigger it from initialize() in the Glance View.

0 _psx_ over 4 years ago

I have the same error but I in my case probably is by my design, flow F:

- app calls background

- BAG temporary event calls webRequest

but from time time to user exits app and enter again so I call F again so temporary event is rewritten and probably than I get BLE_REQUEST_CANCELLED

jim_m_58, can you answer to my 2 post, the are connected with this one

https://forums.garmin.com/developer/connect-iq/f/discussion/279421/is-background-killed-when-new-version-of-app-is-installed

https://forums.garmin.com/developer/connect-iq/f/discussion/279652/makewebrequest-context

0 jim_m_58 over 4 years ago in reply to _psx_

The background should run no more than once every 5 minutes, and when the background runs, it's independent of the main app running or not running.

This one is different as there is no background service involved (or so it sounds to me)

0 6545774 over 4 years ago in reply to flogazo

In the end I did the web request 100ms after the view loaded with a timer, it was never something I could replicate in the simulator and not all models were affected (eg. my 645 music never had any issues)