Without users' permission for communications, will a sideloaded app have the ability to make web requests?

Hi, let me describe my situation. I am adding a feature for my app that is in the ciq store already to enable users pay on the watch. Each time the users need to make a web request at first.

Previously, my app didn't have the Communications permission. Now I wanna test on a real device after some successful simulator tests. But I don't have a trial app in which case sideloading helps. When I sideloaded my app, it would show -2 after a web request. I looked up in the apidoc, -2 means BLE_HOST_TIMEOUT. What does it really mean? If it was caused by my https interface latency,or the absence of Communications permission. It seems to be the latter one. Did you encounter the similar issue?

Yesterday I released a new version. But I saw 0 on one user's watch and most time -2 was thrown. no idea about what happened. When checking the log of my server, I found the request was received already. How to debug this make image request issue? Do you have any idea?

I have seen sth JIM_M_58 posted last year like below.

Another thing is with the current Android, images processing is no longer done on the phone but on a garmin server.

Thins bug report gets into some of the image processing stuff:

https://forums.garmin.com/developer/connect-iq/i/bug-reports/connect-mobile-4-40-makeimagerequest-localhost-error

my question is . In China, where is the server for processing the makeimagerequest image processing? My server is in China, will it caused by the network latency from garmin server to mine?

Top Replies

jim_m_58 over 3 years ago in reply to li2niu +1

There user doesn't confirm permissions with side loads.

Working in the sim does not guarantee that it will work with Android or iOS GCM.

All Replies

0 jim_m_58 over 3 years ago

You need the permission to do a makeWebRequest.

What -2 usually means is that the request was made but there was no response. This can be due to a malformed request as Android and iOS can have a few different issues, like what's part of the URL and what's a param.

0 li2niu over 3 years ago in reply to jim_m_58

jim_m_58 said:
ke what's part of the URL and what's a param.

I can get the point of this part. Due to security policy, the url should be https and only a few http interfaces whose domains point to garmin related sites. My web request works fine in the simulator ,would it be malformed? :< Although I know there are difference between the sim and a real device

You need the permission to do a makeWebRequest.

I added the permission request at first, but perhaps this only takes effect after users' comfirmation, right?

<iq:uses-permission id="Communications"/>

I determine to upload my app to the store for a final test

0 jim_m_58 over 3 years ago in reply to li2niu

There user doesn't confirm permissions with side loads.

Working in the sim does not guarantee that it will work with Android or iOS GCM.

0 Robin_ over 3 years ago

As Jim said -2 can be for a number of errors, but i think its essentially saying i tried to talk to the phone/paired device to send the HTTP Request but got nothing back, different to i got a HTTP Responce (error or otherwise), on IOS i've had this a few times which is usually fixed by closing the connect app on the phone/device and re-opening them which can get it going,

0 li2niu over 3 years ago in reply to Robin_

Last night I release a new version. Now I got 0 UNKNOWN_ERROR on a user's device, no idea about what happened. When checking the log of my server, I found the request was received already. How to debug this make image request issue? Do you have any idea?

0 li2niu over 3 years ago in reply to jim_m_58

Uncle Jim, do you know any more approach to print detailed error messages for the makeImageRequest except the response code. It is really annoying.

0 li2niu over 3 years ago in reply to jim_m_58

I saw 0 on one user's watch and most time -2 was thrown.

0 jim_m_58 over 3 years ago in reply to li2niu

Response code is all you got, unless you can print some debug stuff on the server end. makeImageRequest are more complex than a makeWebRequest as the image processing is done on a garmin server. Mae sure you have the latest SDK, extension, etc.

0 li2niu over 3 years ago in reply to jim_m_58

I am using 4.1.1 Maybe I should downgrade the sdk

0 li2niu over 3 years ago in reply to jim_m_58

But I have added new models so no way backwards.