Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

[Access token] Invalid signature but mine and debug signature are equal

ANSWERED

Hey guys!

I read a lot of "invalid signature or token" threads, but no one seems to solve my problem.
When I start to call for the access_token via my post to https://api.fitbit.com/oauth/access_token I get the written error message. But when I use the debug tool provided by fitbit it gives me the same signature I am using for my application.

I don't know what I should do anymore since it seems to be right.
Maybe you got any other ideas?

Thank you!

Best Answer
0 Votes
1 BEST ANSWER

Accepted Solutions

Though no one seemed to be able to help me I went into further debugging and solved my problem by creating an instance of a token object from the beginning of my OAuth authentication cycle. From now on I just overwrote the new access token and used this object straight up to every signing request and now it is working.

I hope this may help some people one time!

Greetz

View best answer in original post

Best Answer
0 Votes
1 REPLY 1

Though no one seemed to be able to help me I went into further debugging and solved my problem by creating an instance of a token object from the beginning of my OAuth authentication cycle. From now on I just overwrote the new access token and used this object straight up to every signing request and now it is working.

I hope this may help some people one time!

Greetz

Best Answer
0 Votes