Hi--
Starting about 2 hours ago, most requests we are receiving for notifications are containing an invalid signature. This also happened twice earlier this month, but the problem subsided within a half hour, but this time its ongoing. There have been no changes on on end regarding this in any of these cases, so I must assume a rogue notification sender or updated algorithm? Please advise. Thanks.
Eric
Answered! Go to the Best Answer.
Best Answer
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
Yes, the push notification signature issue has been fixed.
Please feel free to turn signature verification back on.
Best AnswerWe are also experiencing the same issue. We have been receiving random or sporadically Invalid Signatures since January 23.
Periods where we received Invalid Signatures:
- January 23 from 10:00AM to 11:00AM (Pacific Time)
- January 24 from 10:00AM to 10:43AM (Pacific Time)
- January 31 from 10:20AM to 12:15PM ongoing (Pacific Time)
The last occurrence is an ongoing issue which ended disabling our Subscriber.
Please review this issue and provide any feedback ASAP.
Best Answer
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
Can you please make sure that the client secret for your app that is specified at dev.fitbit.com is still up to date?
Best Answer@IoanbsuFitbit - what do you mean by "is still up to date"? we made no changes to the application. Why would the secret change?
Best AnswerHi--
There have been 0 changes in our account OR our code in when these issues have occurred. The only changed that has occurred is that because of this issue, we were disabled twice -- I've re-enabled now twice. Our outages map exactly to the first poster's dates and times, so it seems like the likely issue is something on Fitbit's end. Can you confirm and resolve? Thanks!
Eric
Best Answer
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
We are working on fixing the issue. We will notify when it is resolved. The quick fix on your end you can do for now is disable signature validation.
Apologies for any inconvenience.
Fitbit fixed the issue and we have re-enabled signature verification already. I can confirm it's been working as expected for the past week for us. Had no issues since we re-enabled it.
Best Answer
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
Yes, the push notification signature issue has been fixed.
Please feel free to turn signature verification back on.
Best Answer