Error -202 on makeWebRequest

I got a report from a user that they are getting an -202 error when using my app. According to the documentation, it is INVALID_HTTP_METHOD_IN_REQUEST with the description "Request used an invalid http method.".

My code uses Communications.HTTP_REQUEST_METHOD_GET as method, with a simple, user-configured URL like http://ip:port/path. The phone is an iPhone, so http without encryption should work, also if that would be the issue usually another error code is returned. Also the URL works fine when entered into the iPhone's browser.

I recently updated my app to Connect IQ SDK 7.3.0, but I myself and other users who already did the update have no issues.

Any ideas what could cause such an -202?

Top Replies

the-ninth 1 month ago in reply to the-ninth +1 verified

OK, now found the root cause of the issue. I am using a long query string in the URL, and it seems under iOS 16 this is causing the -202 error. When removing the query string it works there. Doing that…

All Replies

0 the-ninth 2 months ago

I was testing now with this user with the same public URL. We have very similar setups, both Garmin Epix Pro Gen 2 with SW 18.14 (he has 51mm, I have 47mm), and both Garmin Connect app version 5.5.0.23 on iOS. A notable difference is that he is on an iPhone X with iOS 16, I am on an iPhone 15 Pro with iOS 17 and now since a few days 18.

0 the-ninth 2 months ago in reply to the-ninth

The issue seems to be related to iOS 16. The affected user tested with another phone with iOS 18 and with that it works.

I'll be testing the fix described here now with the user, maybe we are lucky and it solves the issue.

forums.garmin.com/.../makewebrequest-error--202-invalid_http_method_in_request

0 the-ninth 2 months ago in reply to the-ninth

Unfortunately the fix described in that post did not work, my user still has the issue. I am not entirely sure if iOS 16 is the problem, I don’t have it and am not in touch with any other users that do. So only got this one user’s report that they get the -202 with their iOS 16 device and it works with their iOS 18 device.

Ideas anyone? Not sure what I could try next.

+1 the-ninth 1 month ago in reply to the-ninth

OK, now found the root cause of the issue. I am using a long query string in the URL, and it seems under iOS 16 this is causing the -202 error. When removing the query string it works there. Doing that may be a workaround but only for devices with sufficient memory for the app. If the query string is removed, the response of the server becomes very large, resulting in issues on older devices, especially in the glance there (that's why I introduced this query string in the first place).

0 flocsy🤠 1 month ago in reply to the-ninth

Ah the query string size. It was an issue back in the internet exporer days... If the api is your's then the easiest fix is probably to turn the api to POST.

0 the-ninth 1 month ago in reply to flocsy🤠

Unfortunately it is not my API, so I have to live with it as it is.

0 flocsy🤠 1 month ago in reply to the-ninth

Yeah, then... I don't know the specifics of the api, but maybe knowing this max size you can try to do smaller requests. I don't know if it's possible, but it might be with a little refactoring of your code.

0 the-ninth 1 month ago in reply to flocsy🤠

Yes, I could split it into multiple requests, which would require additional code but could work.

But for now I'll wait and see. My app does not have a big user base, and for now the only user who reported this has a Garmin watch with sufficient memory to process the full response of the server even without the query string. Real problem will be if I have a user that has the older iOS version AND an older Garmin watch with less memory. I'll cross that bridge once that happens.