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
  • over 5 years ago in reply to FlowState

    Sorry, I meant:

    "HTTPS  is only *enforced when you're going out to the real, external internet, not staying on your own local network."

  • over 5 years ago in reply to jim_m_58

     

    "That's a bit different in that it would mean allowing HTTP through GCM to an external server vs localhost and it seems right now, they are only looking at an exception but just for localhost. In your case, it would mean allowing http in general"

    Not necessarily -- Apple Transport Security (which is driving all of this) allows HTTP connections for IP addresses, .local domains, and unqualified domains -- likely for exactly the kind of use cases that ppl are discussing in this thread.

    It seems that Apple only enforces HTTPS for fully qualified domain names.

    In other words, HTTPS is only unenforced when you're going out to the real, external internet, not staying on your own local network.

  • over 5 years ago in reply to Stephen.ConnectIQ

    Hello, is there please some news or plans regarding this topic? We literally loosing money in these peak seasons days, so I would like to update our strategy regarding this as we so far failed to find usable solution for our Locus Map for Garmin on our side. Thanks

  • over 5 years ago in reply to jim_m_58

    This is not a solution for me:

    Although i think a pi is the most used hardware for domoticz,  it also runs on other hardware, which will also be in use by my base 

    Furthermore it is a standardpackage with a http/json interface.  

    I wrote down this use case here since in my original post on the garmin forum a developer wrote down that progress for solving will be tracked in this thread and i want to make sure my use case is known here

  • over 5 years ago in reply to akamming

    That's a bit different in that it would mean allowing HTTP through GCM to an external server vs localhost and it seems right now, they are only looking at an exception but just for localhost. In your case, it would mean allowing http in general

    But if a raspberry pi is involved, with CIQ 3.1 you do have an alternative.  Talking to the raspberry pi over BLE. 

    I'm working on a basic sample of a Garmin device doing just that. where a CIQ app can run python scripts on the raspberry pi for example.  See https://forums.garmin.com/developer/connect-iq/f/discussion/164904/would-you-like-some-pi-with-your-app