03-23-2016 21:44
03-23-2016 21:44
G'Day
I have number of users in our system that contains invalid refresh tokens due to fitbit timeouts and we are moving our backend infrastructure.
Is there a way to get our members un-subscribed from subscription notification that our backend established when member signed up with our services.
We thought if we ask members to go to their fitbit member page and De-Authorize our app then they can login again and in our new infrastructure and we can re-establish the fibit notification subscription.
We tried this and we still get user is already subscribed error:
Attempted to subscribe to Fitbit (public member id: 8a04997653a1a1030153a1b08e920002), but subscription already exists under id: 8a04888a5316f3db01532a43b83d004d
How can we fix this, any ideas anyone?