makeImageRequest with -2 responsecode

I have an app that requests images from the web and displays them. It was working normally for three years. However, last week I saw that it doesn't work anymore. On the simulator it works, but on my Fenix 6X Pro responseCallback function returns response code -2. What does -2 mean and what do I need to do?

Top Replies

jim_m_58 over 5 years ago in reply to jim_m_58 +2

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…
sis651 over 4 years ago in reply to li2niu +1

It should have some specific reason. Server locations may cause some latency but it'll work in the end.

All Replies

sis651 over 4 years ago in reply to VAW.BE

My problem seems to be related to https issue. I switched to some HTTPS source and know it works. If I use my non https website, it doesn't work.

VAW.BE over 4 years ago in reply to sis651

Ok I see, but that's not the issue on my end, as I'm already using HTTPS here for retrieving the image. Really wonder why I might get that -2 error.

VAW.BE over 4 years ago in reply to VAW.BE

For if someone else stumbles upon this: I requested an image via an url that created a dynamic image. Because of the dynamic part, somehow makeImageRequest could not handle that. So I've created a separate server which downloads that image to a new url, and send that new url of the generated image to the watch. Then request that static image from that new url with makeImageRequest. Once downloaded, delete the image from server.

sis651 over 4 years ago in reply to VAW.BE

My problem link was also cropping another linked image and sending it.

li2niu over 4 years ago in reply to VAW.BE

Same Issue

li2niu over 4 years ago in reply to jim_m_58

Oops, my server is in China, and I dont know where is garmin's processing server for ciq users in China......

sis651 over 4 years ago in reply to li2niu

Here, processing server is api.gcs.garmin.com. It's pinging 20 ms from me. Probably some server in İstanbul or some farther place, previously it was 40 ms.

You can traceroute it. The address is probably same but path is different depending on the CDNs.

li2niu over 4 years ago in reply to sis651

It looks fast as well

li2niu over 4 years ago in reply to sis651

The domain for China mainland is https://api.gcs.garmin.cn, It is pinging 20ms for me too. But I still cannot use makeImageRequest now

sis651 over 4 years ago in reply to li2niu

It should have some specific reason. Server locations may cause some latency but it'll work in the end.