Basecamp cannot see or import .fit files since firmware update 6.2

I experience the same issue. Mac OS and Basecamp, Edge 820 on Firmware 6.2.

Had to export GPX file from Strava, this I could import. Direct import from "Activity" folder on Edge 820 does not work anymore.

Basecamp was last updated in 2016... things change. If you're lucky they will update Basecamp. This is really a Basecamp issue rather than an Edge 820 issue though.

fit files: no longer direct import from "Activity" folder with 6.2 firmware update

I've had the same problem and have been on the phone twice with Garmin and they have basically said it's not on them. But with the firmware update to 6.2 I can no longer direct import .fit files from "Activity" folder on Edge 820. I need to be able to do this in order to get the files into certain 3rd party programs. Since it works for Garmin's own Connect they have said they cannot help and that nothing should have changed. Something DID change however in their .fit protocol from version 5.2 to 6.2. Is anyone else having this same problem?

While I sympathise with your problem, if the files work within Garmin's system then the problem does indeed lie elsewhere. Garmin makes changes to the .fit file format on a regular basis (not sure what they might have changed this time), which puts the onus on 3rd parties to adapt. By all means keep beating up on Garmin, but you need also to beat up on your 3rd party to get them to be able to accept any changes that Garmin might have made.

Garmin updated the FIT protocol recently across a number of the Edge units and watch units. Basically any unit that supports Connect IQ. This change was made to allow Connect IQ developers to write data in to the FIT activity file.

This moved the FIT protocol version from 1.0 to 2.0.

Developers will need to update the version of the FITSDK that they are using to a version that supports FIT protocol 2.0 in order to handle this change. I believe that this is the first protocol change made to FIT since it was released.

Anything build using FIT protocol 1.0 will typically stop processing the file when it sees that it is written using FIT protocol 2.0.

Developers will need to update the version of the FITSDK that they are using to a version that supports FIT protocol 2.0 in order to handle this change. I believe that this is the first protocol change made to FIT since it was released.

The developers from Garmin itself will need to update the version of Basecamp!
Basecamp is not made by a third party. Basecamp is TM Garmin.

Correct, in order for Basecamp to support the FIT 2.0 protocol it will need an update.

I have made contact (26-03-2017) with Garmin about the Basecamp problem. They said that they send my mail to the technical division.

I also made contact with the maker of the excellent QMapShack program and they did the trick all ready:

Ivo updated the FIT code in the repository. This will be fixed in the next
release. The impatient ones have to compile QMapShack from the repository
code.
Looks like Ivo is faster than Garmin ;) I just updated Basecamp and it still
can't display new FIT files
Oliver

So QMapShack can now handle the new Garmin fit files.:)

Are there news to FIT 2.0 protocol and basecamp?

That is a question for the Basecamp forum surely?