Complete
over 4 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

Parents
  • As far as blood glucose monitoring, just the other day someone asked me about that in relation to the new BLE stuff in 3.1, as more and more meters have BLE. I've not looked into it myself, but have used the BLE in 3.1 a fair amount.

    This might be something to consider vs trying to use HTTP and pulling the data off the phone. 

Comment
  • As far as blood glucose monitoring, just the other day someone asked me about that in relation to the new BLE stuff in 3.1, as more and more meters have BLE. I've not looked into it myself, but have used the BLE in 3.1 a fair amount.

    This might be something to consider vs trying to use HTTP and pulling the data off the phone. 

Children
  • I am having same problem, using makeWebRequest with an http-server in the internet returning an JSON, this since some weeks.
    How can I switch this Windows 10 IIS http server to https?

  • The devices may or may not be fully compliant with Bluetooth, and given my experience with web requests that aren't fully 'kosher' and Garmin not wanting to support them (despite every other platform supporting them), I have no desire to go down that road. Though I'm sure someone will eventually.