MapRunG Issues - "Get Track from Garmin" (Jan 2026)

[Peter Effeney]

We are receiving a number of reports of users getting errors after using MapRunG on their Garmin watch.

"Get Track from Garmin" is giving an error.

To help isolate the root cause, we are seeking reports from users to help in the diagnosis.

We have had similar issues in the past, and as issues have been identified, normally due to changes in the FIT file format, we have released a new version of MapRun on the phone to be able to interpret the changed file format.

The latest issue is most likely:
- another change in FIT format (that only flows through to us when users upgrade their Garmin firmware), and/or
- an issue introduced in v1.9.1 of MapRunG
(Or some combination of the above).
Note that Garmin has unique versions of firmware for each watch type, so not all watch types are likely to be affected at the same time.

I see good results coming through from MapRunG v1.9.1, so it is not a definitive bug in MapRunG. But until we can learn more, we can’t be sure….

It’s complicated by the fact that people having the issue won’t have an uploaded result (generated by “Get Track from Garmin”), so we need to hear from users.

What helps is details from users:
        - Name
        - Event name
        - Watch type
        - MapRun version (on phone)
        - MapRunG version (on watch)
        - Their FIT file if they can provide it (See instructions below)
        - Any other context (eg just got a new watch? Upgraded something? First-time user?)
               
Please either post reports here or email [e-mail] (Send FIT files to this address).

WORKAROUNDS

Assuming MapRunG performed on your watch, and the issue is getting a result in the Event (normally via "Get Track from Garmin"), the workarounds are:
- Ignore the warning/error and try to upload anyway. The upload should generally work but it comes with a “zero” result, no controls punched and then you need to do a HITMO for every control including S1 and F1.
- Otherwise you need to get the GPX file of your run and generate a result from that.
- The simplest approach to use the GPX file is, if you sync your Garmin activities to Strava:
                - Use the function in MapRun > Show Results > Create Results from Strava Track.
- If you don't use Strava, follow the steps below "To Extract a FIT file" but instead of selecting "Export File", select "Export to GPX”.
                - Then go to: https://console.maprun.net/#/gps_track_upload_without_rg and create a result in the event by uploading your GPX file.


To Extract a FIT file:
        - On your PC/Mac, browse to Garmin Connect at https://connect.garmin.com.
        - Sign in.
        - Go to Activities (this generally shows your most recent activities at the top).
        - Select the relevant Activity - which should display the track and other details.
        - Tap the Cog-wheel icon on the top right to display settings.
        - Select "Export File" to download a ZIP file to your PC/Mac.
        - Attach that file to an email to [e-mail].
        - In the email, include the details requested above.

Peter

[Peter Effeney]

An update on this issue.

It appears that the FIT file that Garmin are providing to us when the user does "Get Track from Garmin" is sometimes corrupt. A valid FIT file can be obtained by using Garmin Connect (website) on a PC/Mac. But this doesn't solve the problem.

We have logged a bug report with Garmin, and have had an active response from them, but no resolution as yet.

In the meantime, see the work-arounds listed in the main post.

Peter

[Peter Effeney]

By way of an update on this....

We have released MapRunG v1.10.0 which takes a different approach to reporting back some of the data from the MapRun event activity run with a Garmin Watch. This side-steps what we think is some reliability in some aspects of Garmin firmware.

To work with this different approach, we have released MapRun v7.10.3 for iOS and Android.

It is recommended that MapRunG users upgrade both MapRunG on their watch and MapRun on their phone.

The different combinations of old/new MapRunG with old/new MapRun v7 should work about as well as MapRunG has been working recently... ie OK sometimes and other times needing to use HITMO or Strava to get a result.

This is quite a change in how MapRunG works ... We've tested various scenarios ... but the proof will be in the feedback from wide-scale usage.

The only note of caution I make at this point is, that it is better to tap the Start button on your watch a reasonable distance from the start triangle to give the GPS etc time to settle and be ready to Start.

Please provide feedback if you have any issues.

Peter

[James-O]

Hi Peter,

I had a MapRunG issue on Tuesday 17th at a UK event (UK > Mole Valley > StreetO 25/26 series), Cobham Mar26 PXAS ScoreQ60. I am using MapRun 7.10.3 and MapRunG 1.10.

I upgraded before the run to both versions and relaunched the apps.

The issue I encountered was that I reached the finish control 58m30s(ish) and the finish control beeped. However when it uploaded to Maprun I had a total time of 1h00m36s. Looking at the fit file there are additional laps at the end, after the finish control, that increase the overall time - my guess is this is the time between the finish control and when i manually exited the MaprunG app.

I will email the Fit file over separately