03-04-2021 08:40
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

03-04-2021 08:40
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
The subscription verification for our application was working fine and we were getting notifications but today it is failing and showing this message "Subscriber has not been successfully verified."
The endpoint is working fine and it is returning the correct 204/404 replies when the code is either correct or invalid. I tried hitting the verify button several times but the subscription is not getting verified.
Oauth client id: 22986P
This is critical for us. Please look into it asap.

- Labels:
-
Subscriptions API
03-10-2021 16:33
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



03-10-2021 16:33
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi @SPHAdmin,
We've responded to the cases you've created through our web form. Please check your email and confirm that you received the appropriate resolution.
Thanks!

03-15-2021 04:46
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

03-15-2021 04:46
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I have not received any resolution yet. I was told that fitbit accidentally disabled some of the subscribers including mine and then re enabled but mine was not. I was asked to recreate subscriber which I did but experienced the same issue. I had no choice but to recreate my app on portal. FYI, the client id is 22C4X4. The verification issue is not there now but now I am experiencing this issue.
ERROR: Authorization failed. Status=400 Response={"errors":[{"errorType":"validation","fieldName":"subscriberId","message":"Invalid parameter subscriberId: null"}]}
The support is not replying on email and on twitter they just take my client id but do nothing. This is really strange that first fitbit accidentally disable the subscriber and now its been 2 weeks that support is not active enough to resolve it.

