Unable to handle a 401 (OAUTH token expired) response

Although you'll probably have to deal with what you wrote above to be on the safe side, but another thing you could try is to prevent the 401 from happening, by saving not only the token but also the timestamp, and when you see it's more than let's say 100 minutes old then call the refreshtoken. This way you should almost never get the 401 (at least not for the expiration reason)

Thank you for replying, yes I have thought of doing that: Store the creation time of the token and refresh it when it gets close to expire. But I'd rather would like to get the error code form the server, there are other error cases that I need to handle. Now I get the -400 responseCode for every error, which is not very helpful. 

I wonder if this problem is only with the particular service provider that I'm using, or if this is a common OAUTH problem in CIQ. I know that CIQ is very picky on the response content, from previous projects.

I implemented the same code in node JS and got the proper error message back. I could not see anything wrong with the 401 response I got back from the web service (due to the expired OAUTH token). Is there a bug in makewebrequest perhaps? 

I can't see anything obviously wrong in the response body data, exept that the body seems to be empty. Still I get the -400 response code in my callback. Here is a screenshot of the HTTP response I get in the CIQ simulator:

and here is the response I get back from my Node JS app, for the same request:
 

Again, I can't see any reason why makewebrequest should return with a -400 (invalid body) status code on this response

So there's no content-type header, nor body in the response.

Nope, body is empty. 

that's clearly not a json response then, is it?

I don't know really (out of my waters here) But just curious: what content type should a reponse have that does not have anything in the body?  

I guess Garmin didn't think about this, only about responses that are json, like: {"status": "ERROR"}