Joe Timmerman
Joe Timmerman
This repository isn't maintained anymore (and also doesn't support Python 3, as you've discovered). I believe the forks [here](https://github.com/moderation/garmin-connect-export/) and [here](https://github.com/pe-st/garmin-connect-export) are more current, I'd give those a try.
HI @Marcski , This repository is no longer being maintained. I ran into a similar issue, and have a [fork](https://github.com/joetimmerman/garmin-connect-export) that includes a "-n" option which avoids this problem by...
I was running into a similar issue (except getting a 204 error). I fixed this for myself in my own fork if you'd like to check it out and modify...
@moderation agreed. Looks like @ebrensi has a fork with Python 3 compatibility and fixes for a few other issues (although I suspect it probably doesn't actually work at the moment...
I ran some tests with my own data and everything looks normal. Did you confirm that you're comparing the files for the exact same activity? How did the files differ?
Hi, You can use the "-f original" argument to export the files in their original format (see fourth example in the readme). This is frequently .fit but obviously depends on...
@Only1nr7 see PR #72
@bxsx Appreciate the feedback, will look into adding a test when I have some time.
@pe-st I think this should be good to go now that I've added in @bxsx 's suggestion to use f-strings matching #78
Hi @parthdesai97 -- if you're still have this problem, it might be worth running with verbose logging enabled to see if that tells you anything interesting. You could also try...