Comments on: Login to the Foursquare API v2 from Android with OAuth http://blog.simonstahl.com/2011/03/16/login-with-oauth-to-the-foursquare-api-v2-from-android/ Just another European geek in Silicon Valley Fri, 13 Jan 2012 05:33:19 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Simon http://blog.simonstahl.com/2011/03/16/login-with-oauth-to-the-foursquare-api-v2-from-android/comment-page-1/#comment-1211 Simon Fri, 13 Jan 2012 05:33:19 +0000 http://blog.simonstahl.com/?p=147#comment-1211 the 2 step process i describe is according the foursquare documentation. there might be other undocumented ways to achieve the same, but there is a risk that this functionality could change in the future. for more information, please see the official documentation: <a href="https://developer.foursquare.com/overview/auth" rel="nofollow">https://developer.foursquare.com/overview/auth</a> the 2 step process i describe is according the foursquare documentation. there might be other undocumented ways to achieve the same, but there is a risk that this functionality could change in the future.

for more information, please see the official documentation: https://developer.foursquare.com/overview/auth

]]> By: suraj g sakhardane http://blog.simonstahl.com/2011/03/16/login-with-oauth-to-the-foursquare-api-v2-from-android/comment-page-1/#comment-1207 suraj g sakhardane Thu, 12 Jan 2012 11:29:46 +0000 http://blog.simonstahl.com/?p=147#comment-1207 Its a wonderful and very helpful post.1 question i was having is that we can make response_type=token in the the following query and get the access token directly (in which case access token is appended to the callback url/registered redirect url ) then why we need to do a 2 step process? https://foursquare.com/oauth2/authenticate?client_id={YOUR_CLIENT_ID}&response_type=code&redirect_uri={YOUR_DEFINED_SCHEME} ie https://foursquare.com/oauth2/authenticate?client_id={YOUR_CLIENT_ID}&response_type=token&redirect_uri={CALL_BACK_URL} gives CALL_BACK_URL#access_token=ACCESS_TOKEN I tried this in the browser n it working.It is asking for authentication and later redirecting to CALL_BACK_URL with access token appended to it! Its a wonderful and very helpful post.1 question i was having is that we can make response_type=token in the the following query and get the access token directly (in which case access token is appended to the callback url/registered redirect url ) then why we need to do a 2 step process?

https://foursquare.com/oauth2/authenticate?client_id={YOUR_CLIENT_ID}&response_type=code&redirect_uri={YOUR_DEFINED_SCHEME}

ie
https://foursquare.com/oauth2/authenticate?client_id={YOUR_CLIENT_ID}&response_type=token&redirect_uri={CALL_BACK_URL}

gives

CALL_BACK_URL#access_token=ACCESS_TOKEN

I tried this in the browser n it working.It is asking for authentication and later redirecting to CALL_BACK_URL with access token appended to it!

]]> By: Simon http://blog.simonstahl.com/2011/03/16/login-with-oauth-to-the-foursquare-api-v2-from-android/comment-page-1/#comment-879 Simon Mon, 24 Oct 2011 21:27:46 +0000 http://blog.simonstahl.com/?p=147#comment-879 i have never seen this error on my side, nor does google return anything when searching for it. you might try to add a path to your url (like simontest-android-app://mypath), but my guess is that the problem lies somewhere else. i have never seen this error on my side, nor does google return anything when searching for it. you might try to add a path to your url (like simontest-android-app://mypath), but my guess is that the problem lies somewhere else.

]]> By: Márcio Martins http://blog.simonstahl.com/2011/03/16/login-with-oauth-to-the-foursquare-api-v2-from-android/comment-page-1/#comment-876 Márcio Martins Mon, 24 Oct 2011 00:01:29 +0000 http://blog.simonstahl.com/?p=147#comment-876 Hi! OAuth Consumer Registration doesn't accept the simontest-android-app:// pattern anymore, returning the following error: Your URL needs a body too (just http:// won't work). Can you advise? Thanks! Hi!
OAuth Consumer Registration doesn’t accept the simontest-android-app:// pattern anymore, returning the following error: Your URL needs a body too (just http:// won’t work).
Can you advise? Thanks!

]]> By: Simon http://blog.simonstahl.com/2011/03/16/login-with-oauth-to-the-foursquare-api-v2-from-android/comment-page-1/#comment-197 Simon Tue, 21 Jun 2011 19:33:33 +0000 http://blog.simonstahl.com/?p=147#comment-197 Hi Rafael oauth works in 2 steps: first you need to authorize your app, then you get the access token. 1. https://foursquare.com/oauth2/authenticate?client_id={YOUR_CLIENT_ID}&response_type=code&redirect_uri={YOUR_DEFINED_SCHEME} 2. https://foursquare.com/oauth2/access_token?client_id={YOUR_CLIENT_ID}&client_secret={YOUR_CLIENT_SECRET}&grant_type=authorization_code&redirect_uri={YOUR_DEFINED_SCHEME}&code={CODE_YOU_VE_GOT_IN_STEP_1} where {YOUR_DEFINED_SCHEME} can actually be anything ("simontest-android-app://" in case of my example) Simon Hi Rafael

oauth works in 2 steps: first you need to authorize your app, then you get the access token.

1. https://foursquare.com/oauth2/authenticate?client_id={YOUR_CLIENT_ID}&response_type=code&redirect_uri={YOUR_DEFINED_SCHEME}
2. https://foursquare.com/oauth2/access_token?client_id={YOUR_CLIENT_ID}&client_secret={YOUR_CLIENT_SECRET}&grant_type=authorization_code&redirect_uri={YOUR_DEFINED_SCHEME}&code={CODE_YOU_VE_GOT_IN_STEP_1}

where {YOUR_DEFINED_SCHEME} can actually be anything (“simontest-android-app://” in case of my example)

Simon

]]> By: Rafael Ramos http://blog.simonstahl.com/2011/03/16/login-with-oauth-to-the-foursquare-api-v2-from-android/comment-page-1/#comment-194 Rafael Ramos Tue, 21 Jun 2011 01:13:46 +0000 http://blog.simonstahl.com/?p=147#comment-194 Hi Simon, Nice tutorial! I was testing your piece of code but right after I give access to my app on foursquare via browser, I'm being redirected to a page that foursquare cannot handle. It says 'we couldn't find the page you're looking for'. And then I never get the token nor my callback url is called. Basically, the url for this 'broken' page is: https://foursquare.com/oauth2/mycallback?code=mycode. Where, 'mycallback' is my callback url (ending with ://) and 'mycode' is actually my code. Do you have any idea of what might be happening? Rafael Hi Simon,
Nice tutorial!
I was testing your piece of code but right after I give access to my app on foursquare via browser, I’m being redirected to a page that foursquare cannot handle. It says ‘we couldn’t find the page you’re looking for’. And then I never get the token nor my callback url is called.

Basically, the url for this ‘broken’ page is: https://foursquare.com/oauth2/mycallback?code=mycode.

Where, ‘mycallback’ is my callback url (ending with ://) and ‘mycode’ is actually my code.
Do you have any idea of what might be happening?
Rafael

]]> By: Simon http://blog.simonstahl.com/2011/03/16/login-with-oauth-to-the-foursquare-api-v2-from-android/comment-page-1/#comment-176 Simon Tue, 14 Jun 2011 04:13:55 +0000 http://blog.simonstahl.com/?p=147#comment-176 Hi there is no need to open the browser again. you can just store the OAuth token in the app after the first login and reuse it the next time. Simon Hi

there is no need to open the browser again. you can just store the OAuth token in the app after the first login and reuse it the next time.

Simon

]]> By: geykel http://blog.simonstahl.com/2011/03/16/login-with-oauth-to-the-foursquare-api-v2-from-android/comment-page-1/#comment-175 geykel Tue, 14 Jun 2011 03:14:49 +0000 http://blog.simonstahl.com/?p=147#comment-175 Hello Simon, Thank you for this great post which helped me a lot to understand how OAuth v2.0 works and how to integrate it to an Android app. I got a question though, I was testing some code that I wrote using your ideas here and everything is working great but I want to change one thing and I want to see if you can give me some directions. My app basically sign in an user to 4sq and then retrieve all the nearby venues, the first time the user sign in, 4sq ask me to authorize my app, that's ok, but next time the user sign in, the app open the browser again (because we are calling an intent for doing that) this time of course 4sq don't ask me to authorize the app because we did that already and just call our custom redirect-uri and give us the access_token... so, what I wanted to ask you is, is there any other way of doing this without open the android browser? at least for every sign in after the first one? which is the one where the user authorize the app (we need the browser for that first sign in)... Sorry for this long comment :) Hello Simon,

Thank you for this great post which helped me a lot to understand how OAuth v2.0 works and how to integrate it to an Android app. I got a question though, I was testing some code that I wrote using your ideas here and everything is working great but I want to change one thing and I want to see if you can give me some directions. My app basically sign in an user to 4sq and then retrieve all the nearby venues, the first time the user sign in, 4sq ask me to authorize my app, that’s ok, but next time the user sign in, the app open the browser again (because we are calling an intent for doing that) this time of course 4sq don’t ask me to authorize the app because we did that already and just call our custom redirect-uri and give us the access_token… so, what I wanted to ask you is, is there any other way of doing this without open the android browser? at least for every sign in after the first one? which is the one where the user authorize the app (we need the browser for that first sign in)…

Sorry for this long comment :)

]]>