Skip to main content

As of about a week ago any workout I have tried to upload to Strava through the API is never being processed. I checked my console log when uploading and I get a response message with a successful response code. The status field states - “Your activity is still being processed.” Here is an example of the response:

success({
    "activity_id" = "<null>";
    error = "<null>";
    "external_id" = "jtw_673D5484-C0C2-40E0-B726-B6E04C98BE86.fit";
    id = 13724712499;
    "id_str" = 13724712499;
    status = "Your activity is still being processed.";
})

When I try to manually upload the same FIT file through my profile it begins “analyzing” the file, but never completes. Also never met with any kind of error code. I have not made any changes to how I am creating these FIT files and they have been processed successfully for over a year up until this point. Has Strava possibly changed/added a required field that I am unaware of?

Also suffering from the same.

Is this due to the removal of API development support going forward ?

@zvbell Have you tried to upload it to other services to check if there might be a problem with the fit file itself? Do you use a official FIT SDK to generate the files? 

Well I had few thoughts down this route - and your reply got me thinking.

So I’ve downloaded from Garmin connect a few of my .fit files that have been uploaded successfully by Garmin directly - as well as a tcx file.   Without using the API, I went to the Strava Webpage and tried to create a manual activity by uploading them,,,

And yep - ‘the file is empty’,  which suggests that the files direct out of Garmin,  as well as from the FIT SDK are not going into Strava correctly when processed by a) my workstation or b) when passed through my home firewall/network.
 

 

Having the same issue - strava support is currently handling my ticket if you want to follow along:
https://support.strava.com/hc/en-us/requests/3098686

OK they just told me they can’t help me on that forum and I have to get help from here🙈

 

​@zvbell  ​@Unshakeable Salt Ltd what are you using to create the fit file?

I’m using a library that was last updated in 2022 (https://pypi.org/project/fit-tool/) - authors’ email address no longer exists.

I’m wondering if there has been a change to the expected format of a .fit file in the last 3 months.

I believe this article confirms my suspicions https://the5krunner.com/2024/02/12/garmin-fit-files-welcomed-improvements-for-2023-4-is-there-a-downside/

 

Strava must have stopped accepting the ‘old’ FIT file format sometime in October.

I guess I’ll have to find another library or fix it myself.

After the official Garmin CSV2FIT converter failed to produce a file that Strava would accept, I gave up and made a CSV2TCX converter and will just use that.

I’m afraid my solution might not be of much help to all of you. I am creating my FIT file inside of an iOS app and am using a 3rd party library ‘SwiftFIT’ to do so. I updated the version of the library I was using and had to adjust my code a bit to fit the new calls. I do not know what was changed within the library, but the previous version I was using was still creating viable FIT files, they just weren’t being accepted by Strava. Now they are.

Interesting. I'm quite sure it's the same situation I was in - using a library that produced FIT v1 vs FIT v2 files. You were lucky to be able to update your library. But I also think there is some additional thing going on since files produced by a (latest version) Garmin CLI tool are not being accepted by Strava.

Strava MUST have stopped accepting v1 without warning. Dev support were not willing to confirm this when I emailed them.

 

Hopefully this thread will provide some guidance to others in the same boat.

Reply


Terms & ConditionsCookie settings