01-15-2019 08:09
01-15-2019 08:09
We have a Subscriber registered to receive notifications of changes to activity data that works fine. We receive the notification from Fitbit servers and then queue a background API call. That is, it works fine for all of our users except one. In their case, we never receive a notification from Fitbit of their changes. We have a raw log that keeps a record of all the requests we receive from Fitbit and their ID does not occur. We have asked the customer to "disconnect" (remove the token in the dashboard at fitbit.com), and then to go through the OAuth process again but this has not made any difference. When we force a manual sync we can access the data via the API. It is just the notifications that are missing (leading to us not syncing). Any ideas?
01-31-2019 08:39 - edited 01-31-2019 08:42
01-31-2019 08:39 - edited 01-31-2019 08:42
Hi @TheRealMrG,
Have you confirmed your application has an active subscription for the user? You can do this by requesting the Get Subscriptions List endpoint. Also, double check the output to make sure the subscription is created correctly (i.e. requesting the correct scopes, the subscription ID is correct, the subscriber id is correct).
Gordon
02-04-2019 03:28
02-04-2019 03:28
Hi @Gordon-C, yes I have a working subscriber in place and am receiving notifications for all other users. It is just one that does not work.
02-08-2019 09:29
02-08-2019 09:29
Would you please private message me the following information. I'll look into the problem further.