Unable to categorize an exercise using custom activities.

[SunsetRunner]

Hi, my standard workflow with activities is the following: i start tracking via my Charge 2 and after the training I do re-classify the activity to one of my personal activity types via the IOS app. This was working fine without any problem until 2.53 was released. Before that, all activities were update properly and i saw the same updated data on the app as well on the web dashboard. With 2.53, i can still change the classification in the app, but after a sync with servers the old classification is pushed to the app. Seems that something is broken with the synchronization logic in 2.53 (maybe linked also to the foot tracking problem?). Cheers

UPDATE:

Small update: this seem to happen only if you change your actitity to a custom one which you defined yourself. If you change it to another standard activity the error does not occur

Moderator Edit: Clarified Subject.

[MarcoGFitbit]

Hello @SunsetRunner, have a warm welcome to the Fitbit Community, it's great to have you on board! 

I appreciate your participation in the forums and your reports about this situation. At this moment I would like to ask you to take screenshots of your exercises before and after categorizing them and reply to me with them so I can check this further. 

Thanks for your patience and understanding, I'll be waiting for your reply. 

[SunsetRunner]

Hello Marco

thanks for coming back to me.

I am attaching 2 screenshots with and without the categorization change.

Yoga is the standard Fitbit activity - "Rückenschule" is my own - customized activitiy. Whenever i am changing Yoga (or another standard Fitbit activity) to my own customized activity (Rückenschule or any other) the app does accept the change, shows it correctly, but only until a sync with the server takes plance - after that the app switches back to the initial actiivty type

As mentioned above, this behaviour is new starting with the new IOS App version. I did this procedure 100 times before without any problem (0% error) but now, with the new app version i have 100% failure

Appreciate your support

UPDATE:

Just saw that 2.53.1 was released. I updated the app and the problem i reported is gone again. So you can close the case. Thanks

[MarcoGFitbit]

Hello @SunsetRunner, I hope you're doing well, I appreciate you have taken the time to reply and send screenshots back. 

Thanks for your participation in the forums, I'm glad to know that after updating the Fitbit app to the version 2.53.1 your issue was resolved! In case you have some spare time, I would like to invite you to visit our Discussions board where you will find great tips and encouragement from other members and if there's anything else I can do for you, please keep me posted!