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

Parents
  • 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.

Comment
  • 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.

Children
  • i agree  with you: The GCM team apparently already fixed for their own use cases (the exeptions for the garmin domains in the network security xml file), so they should just apply the simple fix i already provided. (and tested on an android sample app).