Ticket Created
over 1 year ago

CIQQA-1662

Bug report: ConnectIQ Api & web request via GCM iOS is not passing http response as plain text

Hello ConnectIQ team,

I use makeWebRequest to proceed an auth process of an oAuth API, where I have to read an bearer token from the WebAPI.

The API responds the token as a JSON value type string. It's not possible to read that value as JSON dictionary. But with the GarminConnect app on a Android phone it's possible to use the parameter HTTP_RESPONSE_CONTENT_TYPE_TEXT_PLAIN to get the http response as plain text to read the bearer token from.

With the GCM app on a iPhone it's not possible. The ConectIQ API returns error code -400 independent of the response type parameter.

As it's not possible to read JSON values from a application/json response body, it's necessary to be able to read the body as plain text and parse it in the app. That's the only possibility to handle WebAPIs not following the ConnectIQ rules.

Please add the possibility of reading plain text responses using the makeWebRequest parameter HTTP_RESPONSE_CONTENT_TYPE_TEXT_PLAIN on iOS platform like on Android.

Many thanks. That will help many developers dealing with WebAPIs which are not completely compatible to the ConnectIQ rules.

Referenze thead with examples:

https://forums.garmin.com/developer/connect-iq/f/discussion/310015/webrequest-how-to-ignore-wrong-response-content-type#pifragment-1298=2

Kind regards

Ronny Winkler

ronnywinkler
Parents
  • over 1 year ago

    Hi

    When you say this is not currently scheduled - (sorry for being a bit to the point here..) does that mean that for half a year there has been knowledge about a bug in your system, that negatively influence developers like Ronny that does a great job making the eco system of Connect IQ live up to the promise that Garmin has made to us as customers - and you decide not to fix it? 

    I do not get it. Or have I misunderstood something? ConnectIQ is meant to increase the value of Garmin products by letting third party developers add features to your products, and when there is a bug hindering them from doing so you decide not to fix it, ever?

Comment
  • over 1 year ago

    Hi

    When you say this is not currently scheduled - (sorry for being a bit to the point here..) does that mean that for half a year there has been knowledge about a bug in your system, that negatively influence developers like Ronny that does a great job making the eco system of Connect IQ live up to the promise that Garmin has made to us as customers - and you decide not to fix it? 

    I do not get it. Or have I misunderstood something? ConnectIQ is meant to increase the value of Garmin products by letting third party developers add features to your products, and when there is a bug hindering them from doing so you decide not to fix it, ever?

Children
No Data