01-01-2019 04:52
01-01-2019 04:52
Hello,
First of all I wish all of you a happy new year! I'm looking forward to do new developments and improvements of my apps and clockfaces in the future with the new APIs!
And I'm already working with the exercise API.
I'm using the following code to start an (userdefined) exercise and want to record the gps data
myGPSFunction = geolocation.watchPosition(locationSuccess, locationError); // GPS-Funktion starten exercise.start(exerciseName, { gps: true });
I'm making sure that the gps connection will be established properly and it works, because I'm using the locationSuccess function and the position data for calculation of the distance run.
When I'm transfering the recorded exercise to the fitbit user profile all data of the run will be transfered except the gps data of the run. - it seems that the data isn't available in the exercise.
Have I do anything else to get the exercise working with the gps data?
Can I access such recorded gps data during development and debugging?
Regards
Capitano
Answered! Go to the Best Answer.
01-08-2019 17:10
01-08-2019 17:10
There's definitely some issue with custom exercises and GPS. Hopefully it will be addressed soon. In the meantime, you can use one of the non custom types which does support GPS.
01-08-2019 17:10
01-08-2019 17:10
There's definitely some issue with custom exercises and GPS. Hopefully it will be addressed soon. In the meantime, you can use one of the non custom types which does support GPS.
01-17-2019 13:52
01-17-2019 13:52
Thanks for the information.
It's just the combination using an own exercise name and get the gps data recorded, so I have to think about using the "run" type...
Do you know when this issue will be fixed? I notices that other bugs has been fixed already...
Regards
Capitano
01-27-2019 03:59
01-27-2019 03:59
Any news on that one? It is not the best experience for my users if they do a custom exercise aka. SUP and see Aerobic as done exercise in the activities on Fitbit.com.
02-09-2019 07:22
02-09-2019 07:22
I'm just preparing a new version of my VirtualPartner that uses SDK3 and I want both use a custom exercise name and transfer gps data to the user profile.
Do you have any news on this topic? Is this now possible for custom exercises or have I still to use provided exercises like run?
Regards
Capitano
02-15-2019 10:01
02-15-2019 10:01
I would be really interested in this as well. I am working on creating a Running App that will display more than just the 3 stats at one time you can currently do with exercise shortcuts, ( I like to see more when i run and i don't like touching the watch to switch stats)
While working on the app in the fitbit studio, the fitbit simulator log always returns this: Exercise type does not support GPS
Doesnt matter if i set it to run or skateboard, it always says that.
02-24-2019 07:26
02-24-2019 07:26
Hello we're still waiting for information on that topic.
Is there a changelog for the SDKs where we can check that issue from time to time?
Regards
Capitano
03-14-2019 11:49
03-14-2019 11:49
any update on this?
03-14-2019 11:55 - edited 03-14-2019 12:12
03-14-2019 11:55 - edited 03-14-2019 12:12
Sorry. Answered to the wrong post
03-20-2019 12:41
03-20-2019 12:41
@JonFitbit @SunsetRunner
Does SDK 3.1 now support gps data recording for custom exercises?
Regards
Capitano
03-24-2019 06:16
03-24-2019 06:16
I don't think this is the case. In the updated reference documentation the custom exercise type has been removed from the list of GPS enabled exercises.
Furthermore, custom exercise types still map to Aerobic in the app 😞
03-25-2019 07:26
03-25-2019 07:26
Well that is **ahem**ty, instead of fixing it, they just remove reference that its supposed to work?
04-01-2020 15:28
04-01-2020 15:28
Has anybody any news about this issue?
I tried to use all "the non custom types" and also a different custom types with GPS option, but doesn't works!
if (exercise.state == 'stopped') exercise.start('run');
console.log('exercise state: ' + exercise.state);
console.log('exercise type: ' + exercise.type);
console.log('elevation: ' + exercise.stats.elevationGain);
//OUTPUT
//exercise state: started
//exercise type: undefined
//elevation: 0
Regards