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 marccardinal

    That should be it, literally. The whole situation is a bit absurd, I suspect that it is one of those organizational nightmare things where one group within the team fully understands the problem and the fix, but all decisions like that are strictly limited to another group that won't ever understand (but will fight type and nail to protect the decisionmaking privilege).

    My GCM is on "ignore updates" until further notice (I can't think of a single feature that an update would bring that would be more valuable than what I get from cIQ localhost connectivity), my usual praise for Garmin is considerably muted.

  • over 5 years ago in reply to akamming

    So a potential fix would be to add: <domain>localhost</domain> to the <domain-config> section?

  • over 5 years ago

    I am working on a brand new application and ran into this issue: https://forums.garmin.com/developer/connect-iq/i/bug-reports/failure_during_transfer (the famous FAILURE_DURING_TRANSFER) so I eventually decided to implement a NanoHTTPD based process for communication between the watch and the android app and now I am faced with the TLS requirement on localhost.

    Is there a fix in sight?

  • over 5 years ago in reply to Brandon.ConnectIQ

    tx for the update, but to be honest i am dissapointed by the lack of progress. I already provided the solution in this thread. Did you test this? What was the outcome? 

    Furthermore: I decompiled the latest APK and i found out there already is alread a network security xml in the APK:

    <?xml version="1.0" encoding="UTF-8"?>
    -<network-security-config>

    -<debug-overrides>

    -<trust-anchors>
    <certificates src="user"/>
    </trust-anchors>
    </debug-overrides>

    -<domain-config cleartextTrafficPermitted="true">
    <domain includeSubdomains="true">garmin.com</domain>
    <domain includeSubdomains="true">garmin.cn</domain>
    <domain includeSubdomains="true">garmincdn.com</domain>
    </domain-config>
    </network-security-config>
    So current behaviour in the latest APK is that clear HTTP traffic is already allowed to garmin.com, garmin.cn and garmincdn.com (which i find worrying btw: Why is there a a need to use plain http to the garmin.com, but thats another topic). So why not fully allow plain http, like the solution i provided above?
    Please do not give a process answer (like we are discussing, we working on it, we created a ticket, etc... ), but a specific answer on the questions i ask.
  • over 5 years ago

     Yes Jim, I am using "you" in Garmin sense of course. Guys are spoke persons for whole Garmin in this manner here, which I am not sure if they are aware. And that goes to my only personal problem here as they do not communicate this issue accordingly. And that unfortunately shows lack of ability to handle support of inter-team CIQ related issues for whole Garmin.

    So as suggested, they should not provide features which they can't handle - just look at Android CIQ SDK. It is broken for almost 3 years and in documentation it is still like there isn't any problem - forcing developers to find out this "hard way". And nobody seems to bother. Do you really think it is ok for the company to run into such issue and not even decide what to do with it in more than month? I personally lost A LOT of money and time because of this already, so yes, I would expect some clever communication from Garmin...