10-30-2020, 01:57 PM
We perform this kind of concatenation now with Fitbit activity syncs, but it's been tricky and is all done on our server, whereas we sync Strava directly from the game because of the amount of data.
The problem is we don't know, when you pause VZfit, if you're ever coming back or even killing the game from the pause menu. So we have to send an update then, which shows up in Fitbit or Strava. What we're able to do with Fitbit is monitor subsequent updates on our server, and if they are detected to have started close to the end of a previous update, we delete the previous update on Fitbit servers and resubmit a combined update.
I can see whether it's possible to do the same with Strava in the future, but you might have better luck with third party merging options. We could more easily add a "don't update Strava on pauses" option but you'd then risk losing your data if you didn't switch to another ride or perform some other action to force an update.
The problem is we don't know, when you pause VZfit, if you're ever coming back or even killing the game from the pause menu. So we have to send an update then, which shows up in Fitbit or Strava. What we're able to do with Fitbit is monitor subsequent updates on our server, and if they are detected to have started close to the end of a previous update, we delete the previous update on Fitbit servers and resubmit a combined update.
I can see whether it's possible to do the same with Strava in the future, but you might have better luck with third party merging options. We could more easily add a "don't update Strava on pauses" option but you'd then risk losing your data if you didn't switch to another ride or perform some other action to force an update.