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

    I also still wait using 4.19 until garmin fixes this most important and obvious use case. Why didnt you include the Oregon 700 in routes for connect or track Submission for explore by the way? So per default, there is absolutely no way to get tracks or points transferred to the device without cable. Why do you even implement wifi then?

  • over 5 years ago

    Brandon, I'm a user of Gimporter / Gexporter, Locus-OUT /Locus-IN and IQreceiver. These Apps provide a missing function that Garmin should have : an easy way to upload GPX or FIT file to watch without Internet access when we are in remote location eg hiking or cycling. Many of Garmin customers need this function. These Apps are dependent on localhost connection. That's why I still have the same problem after updating to 4.22. I have reverted back to 4.19 and will remain until this problem is resolved with solution for localhost connection access. I hope you can advocate strongly on our behalf to resolve this.

  • over 5 years ago in reply to Horsetooth

    Good to hear—if anyone else must use "localhost", please let us know.

    I acknowledge that there's room to improve between GCM and the Connect IQ team, but they've generally worked well with us, particularly in more recent times. I think this particular issue was glaringly bad for a number of reasons that have already been discussed. Despite some of the recent turmoil, I'm optimistic that we can do things better.

    There are internal beta testing teams for GCM, but it hasn't been well-coordinated with Connect IQ to regularly verify CIQ-related fixes. I'm going to see what I can do to work on that.

  • over 5 years ago in reply to Brandon.ConnectIQ

    For my apps I explicitly used 127.0.0.1, although users can type localhost in, they don't need to, so current gcm is acceptable. What is unacceptable to me is the lack of what seems like it should be basic networking and/or Android knowledge on behalf of the folks doing gcm. And in addition they should be beta testing their releases to developers at a minimum. Imo there needs to be a whole new layer of accountability of gcm to connect iq.

  • over 5 years ago in reply to Stephen.ConnectIQ

    An exception was added for 127.0.0.1 but not for the "localhost" domain. My fault for poorly communicating the solution--as I'm sure we're all aware, these are commonly used interchangeably, but they're not quite the same. I've edited the solution above for accuracy.

    For folks like , is "localhost" explicitly required? I understand that not everyone here controls/develops the mobile apps being leveraged by their Connect IQ apps, so there may not be an option to use anything other than "localhost" in those cases, correct?