The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.
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?
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.
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.
Best Answer