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

Coleman.Apps over 4 years ago

Hey. I've got this captured in a ticket. We will try to reproduce this this week and figure out where the issue is. Because it works in the sim I'm guessing that it's a device specific bug, but we will figure it out. It sounds like the bug is actually the getSystemStats() giving you the wrong info.
- Cancel
- Up 0 Down
- More
- Cancel

Comment

Coleman.Apps over 4 years ago

Hey. I've got this captured in a ticket. We will try to reproduce this this week and figure out where the issue is. Because it works in the sim I'm guessing that it's a device specific bug, but we will figure it out. It sounds like the bug is actually the getSystemStats() giving you the wrong info.
- Cancel
- Up 0 Down
- More
- Cancel

Children

tomaskafka over 4 years ago in reply to Travis.ConnectIQ

Thank you!
- Cancel
- Up 0 Down
- More
- Cancel
Travis.ConnectIQ over 4 years ago in reply to Coleman.Apps

I've made a fix for the issue of the background app memory limit being incorrect. This affected a few devices because the limit wasn't being explicitly set in devices.xml, and the default value had changed.
- Cancel
- Up +1 Down
- More
- Cancel
tomaskafka over 4 years ago in reply to jim_m_58

Yep, seems like a bit lazy error handling in makeWebRequest.

The RAM is mispresented in simulator, latest 3.0 sdk and all previous versions. Only now I noticed that the watch returns the bg RAM correctly.

Many thanks for helping me debug and fix this!

If you're interested please send me your email to [email protected] and I'll be glad to give you a lifetime Pro license of Weathergraph

apps.garmin.com/.../2de2ee03-0f81-4668-b885-120def9f07c4
- Cancel
- Up 0 Down
- More
- Cancel
jim_m_58 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?
- Cancel
- Up 0 Down
- More
- Cancel
tomaskafka over 4 years ago in reply to Coleman.Apps

Hi Coleman, I now have a working theory, see the above comment. So far it seems to me that:

- getSystemStats() in background service is plain lying and reporting about 100 kB more RAM than the app can really use.

- when makeWebRequest fails because it runs of RAM, the app gets BLE_REQUEST_TOO_LARGE instead of some more specific error message.
- Cancel
- Up 0 Down
- More
- Cancel