Subscription is enabled, but no data is pushed / pinged?

[oakleaf1337]

Hello,

we have followed the guidelines to integrate the subscription model for our application, and everything seems to work fine, but now we've found that a couple of our users are not sending their new steps automatically to our backend ("pinging us") properly.

I'd say 50% of the subscribers works fine, but for some of them, even when we've checked so they're subscribing to our service, (we've verified this "manually" through the /1/user/-/activities/apiSubscriptions.json endpoint).

In the Fitbit-app-console, we can see that there's data pushed to our service, but we cant figure out which users data that's been pushed/pinged to us. 

Is there a way for us to know which users subscriptions that doesnt work as expected, somehow? Are we missing something here, since it works about 50% of the times?

Thanks

[TATeam]

I am having the same issue. The last ping that I have received was on October 6.

[W2E-team]

<Reply removed by the author>

[oakleaf1337]

It seems NO data is pushed at all and has not been pushed since April this year. I re-did the verification process of our webhook URL, but no new data or anything pushed.

Our other 2 apps, with the exact same approach, works fine though. And when we check if the users are subscribing, we're getting bool true on everyone.

[Gordon-C]

Hi @oakleaf1337,

I'll be happy to help you debug this problem.   Would you please private message me your client id, one of the user ids that you're not receiving the notification, and the subscriber endpoint this user is associated.  

Gordon

[Gordon-C]

Hi @TATeam,

Since your problem could be different, please verify the following information

1. Confirm that Fitbit is able contact your subscriber endpoint. You can do this by clicking on the 'details' link by your subscriber list on your app details page.
2. Confirm that your application actually does have active subscriptions for the users. You can do this by requesting the Get Subscriptions List endpoint.
3. Check to see if the users have recently synced their device. You can do this by requesting the Get Devices endpoint and looking at the lastSyncTime value. If they're not syncing, you're not going to get notifications for them.
4. Confirm that your application is processing all of the notifications inside a subscription notifications request. Remember that Fitbit can send multiple notifications inside of a single request.

Gordon