500 error on strava export

Issue #47 resolved
Former user created an issue

I just registered (pmidgley) to test integration between Concept2 logbook and Strava (as per the strava feature request thread we have both commented on). I am able to import from Concept2 logbook, and can export to CSV, but get a 500 error when trying to export to strava (and also export to TCX file). Many thanks for setting this up.

Comments (15)

  1. Sander Roosendaal repo owner

    Hi

    The Concept2 bug is fixed, but your bug report talks about Strava export.

    Best regards, Sander

    PS I am interested to know about your background and how you use the site

  2. Kellen

    You're right, the error still exists on Strava export, however the file still appears in Strava.

    I was confused between two bug reports, apologies.

    I'm a novice indoor rower, with a background in swimming, cycling, and XC skiing. Between the cycling, and being an Engineer, it makes me like the data. I chose indoor rowing as a new sport in large part because of the ability to collect physiological data. You're providing a great service, thank you!

    Kellen

  3. Sander Roosendaal repo owner

    Put some error tracing in the code. Hopefully this will generate some insights in the origin of the error.

  4. pmidgley

    Hi Sander,

    I tried this again today, and got the same error - maybe your error tracing will have picked up something?

    Paul

  5. Sander Roosendaal repo owner

    Will have to look at it later. I have let the site run without updates over the Holidays period. Now is time to get back to open issues :-)

  6. Sander Roosendaal repo owner

    I just checked and the error catching code didn't catch a single error! I need to check in different places.

  7. pmidgley

    Fantastic! That's it working now - I managed to import both my test workouts to strava & shows power, heart rate, cadence & speed graphs nicely. Many thanks for fixing this. Paul

  8. Sander Roosendaal repo owner

    OK thanks. I see some nameError errors in the error log, so I will keep the issue open a little longer, until I find the source of the nameError.

  9. Log in to comment