• State Verified Answer
  • Replies 13 replies
  • Subscribers 18 subscribers
  • Views 1608 views
  • Users 0 members are here
Options
Related

Authorisation Failure

Dreuw
over 3 years ago

I have an app that uses makeOAuthRequest as the first step in downloading data from third party websites.

It works like clockwork using my Android phone on two third party sites.

It fails like clockwork using my iPhone on two third party sites.  Each time I get a call back after making the makeOAuthRequest call BUT the responseCode = 503.

Both sites are clearly not temporarily unavailable so I strongly suspect this to be an Apple <=> Garmin issue.

Have any other developers noticed this problem and is it being investigated by Garmin / Apple?

  • 0 over 3 years ago in reply to Dreuw

    Seems she also thinks it could be server specific:  You really need to take a chill pill Rolling eyes

    3 days ago

    I apologize, I was pulled onto something else last week. I wasn't able to reproduce on our Oauth test app so it seems to only be affecting Oauth calls to certain sites hence my question.  After talking to one of our engineers I was wondering if you know if you are still getting the correct response data even with the page returning 503. 

  • 0 over 3 years ago in reply to jim_m_58

    Something else is that even reported/verified bugs can take time to fix.  If it's the SDK, maybe a few weeks.  If it's GCM, maybe a couple months (it's a separate group from CIQ with their own priorities).  If it requires a FW change, that could be a very long time to make it to all the different devices.  Some devices might get only 1 update a year.

  • 0 over 3 years ago in reply to jim_m_58

    More than one server involved, only iPhones, Postman returns codes as expected.  I think you have taken too many chill pills!  Some of your ideas are daft.  Different parameters for different phones on making an OAuth request.  Really?  The code is phone agnostic and rightly so.  The funniest suggestion you made was in the context of my other complaint, that lap swimming is supported properly in the API, where you suggest using the compass to determine lengths.  Do you think it might be better for the community if you were less active on here?