Complete
over 4 years ago

WERETECH-7625

Future 3.1.1 Release

Started getting a lot of BLE_REQUEST_TOO_LARGE - outgoing makeWebRequest doesn't even pass to server

Hello, recently (after some firmware or Connect app update?) I started getting BLE_REQUEST_TOO_LARGE (code -102) as a response to my makeWebRequest (it's a request from watchface's background service). 

The server doesn't even register this request, which means that it doesn't pass from watch. However, the url (https) is now only about 160 characters, and it has worked without problems for about a year.

Is there anything I can do to even debug this? Is there a known bug (Vivoactive 3) about this?

I tried shortening the request url as much as possible (it is now about 140 bytes), but no improvement, and much longer urls worked for me in the past.

tomaskafka
Parents
  • over 4 years ago in reply to tomaskafka

    I think it depends on what runs out of ram.  Sound like here it might have been when you called the makeWebRequest and it didn't have the memory it needed to bundle up the request and pass it on.

    If you run out in your own code, you should get an "out of memory".  It's been a while since I ran into that case myself.

    By the way, where you seeing the bogus 100kb of memory in the sim or on the va3?  If the sim, which SDK?

Comment
  • over 4 years ago in reply to tomaskafka

    I think it depends on what runs out of ram.  Sound like here it might have been when you called the makeWebRequest and it didn't have the memory it needed to bundle up the request and pass it on.

    If you run out in your own code, you should get an "out of memory".  It's been a while since I ran into that case myself.

    By the way, where you seeing the bogus 100kb of memory in the sim or on the va3?  If the sim, which SDK?

Children