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
  • 4.20 incremented the targetSdkVersion from 27 (Oreo) to 28 (Pie), which is where Google flips the defaults on allowing http, similar to what Apple is doing. Kudos to Garmin for giving an early heads-up, since cIQ devs are not necessarily experts in both iOS and Android.

    The fix on Android should literally just be a configuration setting (implication: the app would not be able to whitelist hosts at runtime), add the networkSecurityConfig exception for localhost and all those local use cases will be fine.

Comment
  • 4.20 incremented the targetSdkVersion from 27 (Oreo) to 28 (Pie), which is where Google flips the defaults on allowing http, similar to what Apple is doing. Kudos to Garmin for giving an early heads-up, since cIQ devs are not necessarily experts in both iOS and Android.

    The fix on Android should literally just be a configuration setting (implication: the app would not be able to whitelist hosts at runtime), add the networkSecurityConfig exception for localhost and all those local use cases will be fine.

Children
  • Me neither.. 

    Any news here? Gosh, I am again so demotivated to invest anything more to this platform. :( Same thing happened last year when I encounter issue of weird compiler behaviour prevented me to continue with my plans with my other app and I got sensible response from Garmin team after 7 months - what a support... That is why I am not in the mood for any compassion in this topic. 

  • >Kudos to Garmin for giving an early heads-up,

    kudos for breaking this now instead of breaking this later?  i don't quite get that.