I was using one web subscription endpoint (lets call it https://one.example.com/X) to receive incoming activity updates. When I was ready to make my app live I updated the URL to be https://two.example.com/Y.
The problem is that I continue to get incoming requests to https://one.example.com/X even though this URL is nowhere in my app description/details/subscriptions, etc. Intermittently I get incoming requests to https://two.example.com/Y
I've since deleted the subscription entry and added a new one that points to https://two.example.com/Y. But I'm perplexed, why would FitBit send requests to an endpoint that is no longer relevant? Its caused some headaches that users are not getting data in my app.
Anyone else see this? FitBit devs: is there an outstanding bug covering this?
