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 in reply to 3719391

    Indeed. Forcing the GMT- instead GMT+ and removing the params passed.

    Initially I missed that the params must be removed, but this way it worked.

    I'm not sure how related it is to the Google API, because it works completely fine with GMT+ on my Android while the same app in the same watch fails with GMT+ on my iPhone.

    Now how make it work on the GMT+? Or will Garmin guys finally fix it after years?

Comment
  • over 2 years ago in reply to 3719391

    Indeed. Forcing the GMT- instead GMT+ and removing the params passed.

    Initially I missed that the params must be removed, but this way it worked.

    I'm not sure how related it is to the Google API, because it works completely fine with GMT+ on my Android while the same app in the same watch fails with GMT+ on my iPhone.

    Now how make it work on the GMT+? Or will Garmin guys finally fix it after years?

Children
No Data