App exported TCX different to web api response

[ryantam626]

I exported an activity log from Android app because I think there was a heart rate sync issue with Strava - the heart rate Strava have gotten is always the same value.

Upon inspecting the TCX file it generated, I see that the Android app exported TCX indeed has a constant heart rate value for the `<HeartRateBpm>` nodes.

Thinking this is an issue with your API, I poked around the API and issued 2 relevant requests.

https://dev.fitbit.com/build/reference/web-api/activity/get-activity-log-list/#Request

https://dev.fitbit.com/build/reference/web-api/activity/get-activity-tcx/#Request

And I discovered that the TCX sourced from the Web API does indeed have seemingly correct heart rate values for the `<HeartRateBpm>` nodes, what gives?

[JohnFitbit]

Hi @ryantam626,

Was the bpm in the TCX file constant throughout the entire activity? Are you seeing different heart rate values in Strava and the Web API?

Could you also PM me the TCX file in question along with your user id? Thanks!

[ryantam626]

Hi @JohnFitbit 

> Was the bpm in the TCX file constant throughout the entire activity? Are you seeing different heart rate values in Strava and the Web API?

BPM in TCX file (exported from the official Fitbit Android app) is constant throughout the entire activity. Strava sees the exact same constant BPM both when the activity is automatically sync'd to Strava, and also when I delete the activity on Strava and reupload using TCX file exported from the official Fitbit Android app (obviously).

BPM in TCX file fetched from Fitbit web api is not constant and seemingly correct.

Will DM shortly - thank you!

[JohnFitbit]

@ryantam626 Thanks for sharing your TCX files. I'm able to see the constant values from the TCX file pulled from the app, and the seemingly correct values from the Web API TCX fetch. I'll go ahead and file a ticket with engineering to investigate the issue and keep you posted once I receive an update.

Thanks again for your find!

[JohnFitbit]

@ryantam626 Just wanted to give you an update. This is still being looked into. 

As a workaround, could you instead pull the TCX from the Web API rather than within the app?

[ryantam626]

@JohnFitbit - Strava seems to be picking up the correct heart rate data now, so there isn't any need for me to export TCX to correct it.

Also it seems the issue has resolved itself for me anyway. As in the TCX exported from Android app is now correct (in terms of heart rate data) once again.