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
  • over 2 years ago

    I verified I'm experiencing this infinite login issue due to being in a GMT+ zone, by manually setting the watch time to GMT- as you stated.

    Were you able to get the "Simply Late" watch face to work in GMT+ by encoding the "+" sign?

Comment
  • over 2 years ago

    I verified I'm experiencing this infinite login issue due to being in a GMT+ zone, by manually setting the watch time to GMT- as you stated.

    Were you able to get the "Simply Late" watch face to work in GMT+ by encoding the "+" sign?

Children
  • over 2 years ago in reply to 3719391

    Hi. I’m not using the “Simply Late” source but just noticed it was experiencing the same issue I was when I was researching.

    See FlowState’s solution below for encoding the query string into the URL (get parameters instead of post). That worked for me.