Comments

3 comments

  • Avatar
    Henry Kim

    I figured it out - the rides I couldn't import were set to Private. I wonder if the error message could point this out? 

    0
    Comment actions Permalink
  • Avatar
    Ali

    Henry - glad that you could figure it out. It does make sense to have a specific error message, but I am suspecting the private route information is not passed from the website when we import. But I will pass this on to the design team to revisit the implementation.

    0
    Comment actions Permalink
  • Avatar
    Jim Ahearne

    @Henry - Thank you for sussing this out. I too was having issues, but didn't notice these were tied to a "Private" setting for the route.

    @Ali - For what it's worth, when I experienced this, in addition to my selected route being private, I was working with  a FIT file. My work around was to export the route from RideWithGPS as a GPX track, rather than FIT file. That worked.

    0
    Comment actions Permalink

Please sign in to leave a comment.