Acknowledged

Garmin Connect Mobile on Android unable to handle MakeWebrequest Comm.HTTP_RESPONSE_CONTENT_TYPE_FIT  on 127.0.01 (localhost)

When using Garmin Connect IQ Apps IQMapReceiver or GExporter for downloading Fit Course files from a mobile (GPX) to a Connect IQ device, it seems not to work as expected anymore.

Issue mentioned is taken into account already: Connect version 4.20 broke local http access?

Problem: When only Bluetooth is enabled in Android and companion device (fenix, edge) you reach the point to request the course list of the fit web server successfully (localhost), (mimetype: application/json).

But when you perform the next step and try to download one course, the web server does not receive the request (mimetype application/fit) and the companion app recieves error code 0 (unknown error). No Fit file can be downloaded to the connect iq companion app.

Workarround:

(1) you need to enable WiFi (internet connection is not required) or mobile data connection. The device will receive an external IP Address. Download works

or                      

(2) you need to turn on WiFi on edge devices and download over WiFi (IP adress assigned)

How to Reproduce:

just use the open sourcce programs from gexporter and perform the steps mentioned in the problem section

Android App to export GPX and FIT to garmin devices

Assumption: the behaviour of Web Requests inside connect mobile has been changed or is broken but not known by many due to the fact that most commercial apps (comoot) are pure web based (not rely on localhost)

Android 12

Garmin Connect Mobile 4.57  

Mobile: Samsung Galaxy Note 20 Ultra latest firmware from July

schlupp73

  •   can you support to check if the Android team could implement our proposal

    For all requests targeting 127.0.0.1/localhost, use a unified pass-through in the BLE proxy regardless of content type. No MIME-type-specific routing or network checks should apply to localhost traffic.
    Note: This requires no additional Android security exceptions — localhost is already exempt from cleartext restrictions, as evidenced by working JSON requests.

  • Please, Garmin, can anything be done about this bug? 
    There are places with no wifi/cell.net signal and since your app can not work without Internet and transfer GPX route into watches, it is quite difficult to plan an activity, hike or route during long trip in mountains.. 
    This app would work well and it is obviously nothing too difficult to encode GPX into FIT file and send it to watches completely offline (and I still do not undestand why there is a need for any external app, why native Garmin Connect can not do it) if only there was not this bug...
    It last years, why could not you fix it and why do you deliberately crippling your not-so-cheap devices? 
    There is no need to move everything to the cloud and it is not possilbe sometimes either... 
    Keep (garmin)Connect doing what it should do and add an offline GPX-to-watches option, or fix this bug, please!

  • It has been more than three years, this bug was postet. Would be great, if the Garmin technicians could solve this issue soon...

  • Now this bug is tagged as "Acknowledged".

    Anyone from Garmin can tell us if is going to be solved soon?