Complete

over 5 years ago

Garmin Connect Mobile 4.22 for Android includes the changes to allow HTTP on 127.0.0.1.

Connect version 4.20 broke local http access?

Getting several reports of functionality no longer working, it looks like Android Garmin connect app version 4.20 may have broken web request to local host via urls like http://127.0.0.1:17580/sgv.json?count=3

Horsetooth

Parents

Horsetooth over 5 years ago in reply to jim_m_58

I don't understand why you are differentiation iOS and Android. We have been using http on iOS as well and it was working fine. I haven't tried it since we started seeing the Android issue but I'd assume Garmin is going to stop it there as well.

I don't control the Android app, or the iOS one, although the Android one at least is open source. Both have been using localhost http to support several watch types, not just Garmin. I won't be working on the Android app but maybe someone else will add Garmin specific companion functionality to it.
- Cancel
- Up 0 Down
- More
- Cancel

Comment

Horsetooth over 5 years ago in reply to jim_m_58

I don't understand why you are differentiation iOS and Android. We have been using http on iOS as well and it was working fine. I haven't tried it since we started seeing the Android issue but I'd assume Garmin is going to stop it there as well.

I don't control the Android app, or the iOS one, although the Android one at least is open source. Both have been using localhost http to support several watch types, not just Garmin. I won't be working on the Android app but maybe someone else will add Garmin specific companion functionality to it.
- Cancel
- Up 0 Down
- More
- Cancel

Children

dcmarti over 5 years ago in reply to jim_m_58

They have never implemented that threat. HTTP was working quite fine with iOS as well as Android. Untill GCM 4.20 at least.
- Cancel
- Up 0 Down
- More
- Cancel
TheDewi over 5 years ago in reply to jim_m_58

There are a lot of discussions online about excluding ATS for localhost, eg: https://bencoding.com/2015/07/20/app-transport-security-and-localhost/

It also seems Apple backed off from the hard https requirement in 2017?

This will also have broken IoT stuff.

What is the recommended way to do inter-app communication now?
- Cancel
- Up 0 Down
- More
- Cancel
Horsetooth over 5 years ago in reply to jim_m_58

I've read it, but it doesn't mean a whole lot to me since it takes about ats which appears to be apple specific and it's also 2 years old talking about something that was supposed to happen 2 years ago. As I said we've been using localhost on iOS and Android every since then without issue, and every other browser and watch in the world still allows it, fwiw.
- Cancel
- Up 0 Down
- More
- Cancel
jim_m_58 over 5 years ago in reply to Horsetooth

Read the 2017 blog post. This started due to Apple and iOS9
- Cancel
- Up 0 Down
- More
- Cancel
Horsetooth over 5 years ago in reply to Horsetooth

btw, I also consider the 8 word official response from Garmin to be insufficient, in case anyone cares, this is the official bug report channel, is it not?
- Cancel
- Up 0 Down
- More
- Cancel