I've just figured out the API and made my first successful weight update (go me!). But now I'm having a few troubles. I was developing locally and after I pushed my code to my live site I tried to submit another weight update but I get a 401 error with the text "This request requires HTTP authentication".
I looked into the issue a bit more and it seems that I wasn't actually being returned an access_token, I was getting and error back with the text : "invalid_request".
I don't know what to do. It might be related to the fact that I tried removing the app from my Runkeeper account to see if I needed to add it again or something. Is removing an app permanent or something?
The app is hosted at http://weighttrail.com/ if you want to see for yourself. It just adds a weight to your profile at the moment when you submit.
* From the authorization endpoint, it means that the "response_type" was
something other than "code";
* From the token endpoint, it means that one or more of the following are
incorrect: client_id, client_secret, code, and/or redirect_uri.
If you send me your client ID, I can look at our logs to see which case is
occurring. Common causes are:
* Attempt to re-use an authorization code (they expire as soon as they are
converted to access tokens); or,
* Not passing the same redirect_uri to both endpoints.
On Mon, May 7, 2012 at 7:23 PM, real_ate <and...@bloo.ie> wrote:
> Hi All,
> I've just figured out the API and made my first successful weight update
> (go me!). But now I'm having a few troubles. I was developing locally and
> after I pushed my code to my live site I tried to submit another weight
> update but I get a 401 error with the text "This request requires HTTP
> authentication".
> I looked into the issue a bit more and it seems that I wasn't actually
> being returned an access_token, I was getting and error back with the text
> : "invalid_request".
> I don't know what to do. It might be related to the fact that I tried
> removing the app from my Runkeeper account to see if I needed to add it
> again or something. Is removing an app permanent or something?
> The app is hosted at http://weighttrail.com/ if you want to see for
> yourself. It just adds a weight to your profile at the moment when you
> submit.
> Any help would be greatly appreciated,
> Cheers!
I had a look back over my code and I think I have everything in place and there is nothing incorrect. I had the exact same code working not so long ago so I don't see what could be wrong.
My client id is 75c81795efb84b93acfde284f604eed1 so if you could have a look at the logs I would be very grateful.
On Tuesday, May 8, 2012 12:35:56 AM UTC+1, Chris wrote:
> "invalid_request" is an OAuth error:
> * From the authorization endpoint, it means that the "response_type" was > something other than "code";
> * From the token endpoint, it means that one or more of the following are > incorrect: client_id, client_secret, code, and/or redirect_uri.
> If you send me your client ID, I can look at our logs to see which case is > occurring. Common causes are:
> * Attempt to re-use an authorization code (they expire as soon as they are > converted to access tokens); or, > * Not passing the same redirect_uri to both endpoints.
> -- Chris
> On Mon, May 7, 2012 at 7:23 PM, real_ate <and...@bloo.ie> wrote:
>> Hi All,
>> I've just figured out the API and made my first successful weight update >> (go me!). But now I'm having a few troubles. I was developing locally and >> after I pushed my code to my live site I tried to submit another weight >> update but I get a 401 error with the text "This request requires HTTP >> authentication".
>> I looked into the issue a bit more and it seems that I wasn't actually >> being returned an access_token, I was getting and error back with the text >> : "invalid_request".
>> I don't know what to do. It might be related to the fact that I tried >> removing the app from my Runkeeper account to see if I needed to add it >> again or something. Is removing an app permanent or something?
>> The app is hosted at http://weighttrail.com/ if you want to see for >> yourself. It just adds a weight to your profile at the moment when you >> submit.
>> Any help would be greatly appreciated, >> Cheers!
On Tue, May 8, 2012 at 4:09 AM, real_ate <and...@bloo.ie> wrote:
> Hi Chris,
> I had a look back over my code and I think I have everything in place and
> there is nothing incorrect. I had the exact same code working not so long
> ago so I don't see what could be wrong.
> My client id is 75c81795efb84b93acfde284f604eed1 so if you could have a
> look at the logs I would be very grateful.
> Cheers,
> - A
> On Tuesday, May 8, 2012 12:35:56 AM UTC+1, Chris wrote:
>> "invalid_request" is an OAuth error:
>> * From the authorization endpoint, it means that the "response_type" was
>> something other than "code";
>> * From the token endpoint, it means that one or more of the following are
>> incorrect: client_id, client_secret, code, and/or redirect_uri.
>> If you send me your client ID, I can look at our logs to see which case
>> is occurring. Common causes are:
>> * Attempt to re-use an authorization code (they expire as soon as they
>> are converted to access tokens); or,
>> * Not passing the same redirect_uri to both endpoints.
>> -- Chris
>> On Mon, May 7, 2012 at 7:23 PM, real_ate <and...@bloo.ie> wrote:
>>> Hi All,
>>> I've just figured out the API and made my first successful weight update
>>> (go me!). But now I'm having a few troubles. I was developing locally and
>>> after I pushed my code to my live site I tried to submit another weight
>>> update but I get a 401 error with the text "This request requires HTTP
>>> authentication".
>>> I looked into the issue a bit more and it seems that I wasn't actually
>>> being returned an access_token, I was getting and error back with the text
>>> : "invalid_request".
>>> I don't know what to do. It might be related to the fact that I tried
>>> removing the app from my Runkeeper account to see if I needed to add it
>>> again or something. Is removing an app permanent or something?
>>> The app is hosted at http://weighttrail.com/ if you want to see for
>>> yourself. It just adds a weight to your profile at the moment when you
>>> submit.
>>> Any help would be greatly appreciated,
>>> Cheers!
On Tuesday, May 8, 2012 10:20:17 PM UTC+1, Chris wrote:
> Andrew,
> Your requests for an access token appear to be missing a redirect_uri. > (You're setting it correctly on the request for an authorization code.)
> -- Chris
> On Tue, May 8, 2012 at 4:09 AM, real_ate <and...@bloo.ie> wrote:
>> Hi Chris,
>> I had a look back over my code and I think I have everything in place and >> there is nothing incorrect. I had the exact same code working not so long >> ago so I don't see what could be wrong.
>> My client id is 75c81795efb84b93acfde284f604eed1 so if you could have a >> look at the logs I would be very grateful.
>> Cheers, >> - A
>> On Tuesday, May 8, 2012 12:35:56 AM UTC+1, Chris wrote:
>>> "invalid_request" is an OAuth error:
>>> * From the authorization endpoint, it means that the "response_type" was >>> something other than "code";
>>> * From the token endpoint, it means that one or more of the following >>> are incorrect: client_id, client_secret, code, and/or redirect_uri.
>>> If you send me your client ID, I can look at our logs to see which case >>> is occurring. Common causes are:
>>> * Attempt to re-use an authorization code (they expire as soon as they >>> are converted to access tokens); or, >>> * Not passing the same redirect_uri to both endpoints.
>>> -- Chris
>>> On Mon, May 7, 2012 at 7:23 PM, real_ate <and...@bloo.ie> wrote:
>>>> Hi All,
>>>> I've just figured out the API and made my first successful weight >>>> update (go me!). But now I'm having a few troubles. I was developing >>>> locally and after I pushed my code to my live site I tried to submit >>>> another weight update but I get a 401 error with the text "This request >>>> requires HTTP authentication".
>>>> I looked into the issue a bit more and it seems that I wasn't actually >>>> being returned an access_token, I was getting and error back with the text >>>> : "invalid_request".
>>>> I don't know what to do. It might be related to the fact that I tried >>>> removing the app from my Runkeeper account to see if I needed to add it >>>> again or something. Is removing an app permanent or something?
>>>> The app is hosted at http://weighttrail.com/ if you want to see for >>>> yourself. It just adds a weight to your profile at the moment when you >>>> submit.
>>>> Any help would be greatly appreciated, >>>> Cheers!
On Tue, May 8, 2012 at 8:08 PM, real_ate <and...@bloo.ie> wrote:
> Hi Chris,
> For some reason I had changed my redirect_uri to redirect_url and hadn't
> noticed. Should this not give a better error saying what the problem is?
> - A
> On Tuesday, May 8, 2012 10:20:17 PM UTC+1, Chris wrote:
>> Andrew,
>> Your requests for an access token appear to be missing a redirect_uri.
>> (You're setting it correctly on the request for an authorization code.)
>> -- Chris
>> On Tue, May 8, 2012 at 4:09 AM, real_ate <and...@bloo.ie> wrote:
>>> Hi Chris,
>>> I had a look back over my code and I think I have everything in place
>>> and there is nothing incorrect. I had the exact same code working not so
>>> long ago so I don't see what could be wrong.
>>> My client id is 75c81795efb84b93acfde284f604ee**d1 so if you could have
>>> a look at the logs I would be very grateful.
>>> Cheers,
>>> - A
>>> On Tuesday, May 8, 2012 12:35:56 AM UTC+1, Chris wrote:
>>>> "invalid_request" is an OAuth error:
>>>> * From the authorization endpoint, it means that the "response_type"
>>>> was something other than "code";
>>>> * From the token endpoint, it means that one or more of the following
>>>> are incorrect: client_id, client_secret, code, and/or redirect_uri.
>>>> If you send me your client ID, I can look at our logs to see which case
>>>> is occurring. Common causes are:
>>>> * Attempt to re-use an authorization code (they expire as soon as they
>>>> are converted to access tokens); or,
>>>> * Not passing the same redirect_uri to both endpoints.
>>>> -- Chris
>>>> On Mon, May 7, 2012 at 7:23 PM, real_ate <and...@bloo.ie> wrote:
>>>>> Hi All,
>>>>> I've just figured out the API and made my first successful weight
>>>>> update (go me!). But now I'm having a few troubles. I was developing
>>>>> locally and after I pushed my code to my live site I tried to submit
>>>>> another weight update but I get a 401 error with the text "This request
>>>>> requires HTTP authentication".
>>>>> I looked into the issue a bit more and it seems that I wasn't actually
>>>>> being returned an access_token, I was getting and error back with the text
>>>>> : "invalid_request".
>>>>> I don't know what to do. It might be related to the fact that I tried
>>>>> removing the app from my Runkeeper account to see if I needed to add it
>>>>> again or something. Is removing an app permanent or something?
>>>>> The app is hosted at http://weighttrail.com/ if you want to see for
>>>>> yourself. It just adds a weight to your profile at the moment when you
>>>>> submit.
>>>>> Any help would be greatly appreciated,
>>>>> Cheers!
