Acknowledged
5 months ago

makeWebRequest: bad request on some devices

https://forums.garmin.com/developer/connect-iq/i/bug-reports/makewebrequest-bad-request-on-some-devices?CommentId=0afa464f-13fb-47f6-83cc-77c5bdc16f11

In makeWebRequest, I am getting a 400 if I am in a +GMT timezone and it works successfully in a -GMT timezone using the GoogleAPIs for calendar events. According to https://stackoverflow.com/questions/30294500/google-calendar-api-doesnt-accept-datetime-with-positive-utc-offset/58860565#58860565, "+" needs to be encoded as "%2B"

Thanks

Heckles
Parents Comment Children
  • over 3 years ago in reply to Heckles

    Good investigation. 

    Unfortunately in my case there is another API call that insists on POST params, so this workaround is not enough for my case and some devices still fail. 

    Namely it's https://oauth2.googleapis.com/token call.

    This bug is specific to a mobile phone app. I have one watch that works with Android phone app but not with iPhone app. Other users keeps reporting this bug as well. 

    Thanks for sharing your findings though. It might help some.