This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Import fails when multiple files are being uploaded from the same start point.

I have observed over the last month or so of manually uploading workouts that if i have more than 2 .fit files of workouts, they fail.
An interesting observation is that it won't fail if the start points are considerably far off(500m+).

There could be a flag check for start point of the workout that is returning an already uploaded response, but this check should also include the timestamp.

My use case is I start my wame up from point A and do a mile loop. Then after a good 30mins or drills etc which are not tracked, I begin my run from within the same vicinity.

While the use case seems pretty common, I'm curious if there's something wrong with what I'm doing.

0 trux over 2 years ago

I do not quite understand why you want to import activities instead of logging them with your watch, but you can import each activity only once. Each activity has an ID, which is unique. You either have to delete the original activity before importing the edited new copy, or you have to change the ID in the cloned activity. Much simpler is recording your activities with your watch. That's what it was built for.