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

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

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