Verified subscription endpoints not receiving any notifications

[StefanS]

Hello,

We've got a new app in development which is configured to receive notifications for the activities, foods, sleep and body collection paths. We also have 3 hosting environments (a local development environment, then a staging environment and our live production environment). We have a subscriber id per collection path per environment, so 12 (4 x 3) subscriber ids. All subscription endpoints verified successfully w/ Fitbit, but the only environment which is receiving notifications upon device syncing or web updates is our local development environment (whose subscription endpoint is accessible via DynDNS and uses http, while our other 2 environments use https). We've been checking our server logs on the 2 non-local environments and there has been nothing received from Fitbit after the verification checks (with invalid and valid codes).

Any idea what would cause a verified subscription endpoint to not be pinged by Fitbit when a registered user syncs their device or logs data on the Fitbit site? Again, our local development environment (hosted up via http over DynDNS) is receiving notifications as expected, but our staging and production environments are not getting pinged with any notifications whatsoever when our registered test users sync / log activity.

Thanks in advance for any help!

-Stefan

[StefanS]

Looks like it might have been a timing issue of some sort? We're getting notifications against our newly added enpoints in our production environment now (as of roughly 12 or so hours after them being verified).

-Stefan

[SACH]

Looks like I'm facing the same issue. We updated our subscription endpoint few hours ago and still not receiving any notification. New endpoint is successfully verified.

We rolled back to the old endpoint thinking this might be some issue in the new endpoint we configured but even going back to the old endpoint which was woking earlier in the morning has the same situation. After verifiying no notifications yet sent.

Glad I found this post.

[JeremiahFitbit]

This is unusual.

Subscriptions are tied to a subscriber. If you add a new subscriber (as opposed to editing the existing subscriber's URL), you need to add a new subscription to that subscriber.