dinasaif / socialauth-android

Automatically exported from code.google.com/p/socialauth-android
0 stars 0 forks source link

a question (Issue with twitter: Unable to retrieve the access token. Status: 401.) #55

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
I has seen the issues 48, and the bug is fixed with the new release 
(socialauth-android-2.1)

But In my case, i checked out your project socialauth-android (not download the 
file jar )  and imported it in my project  So I would like to know how to fix 
the problem in the source code.  

Could you tell me what you have changed in the source code 
(socialauth-android-2.1) to make the twitter work 

best regards

Jack luo 

Original issue reported on code.google.com by luoshaoD...@gmail.com on 18 Apr 2013 at 2:58

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
Same problem here, and for me there is also the 
http://code.google.com/p/socialauth-android/issues/detail?id=54. Which I am 
betting is also related to anything you guys might have changed in the 2.1.jar. 
I'm investigating this myself now since I need a fix urgently, but would also 
implore you to respond with a solution ASAP since this is a big issue.

I'm guessing it has something to do with the callback URL, since in the log it 
still shows me your default dummy URL, whereas I have a different one set in 
the twitter app settings.

And when I switch back to your testing consumer key and secret, I can send 
tweets again, but still can't update facebook status.

Original comment by matej.di...@gmail.com on 19 Apr 2013 at 10:45

GoogleCodeExporter commented 8 years ago
Hi , Previously we were using twitterapp: connect but now as per latest api 
changes the callback url should be same as with ur account.

so if you the new jar avaialable , containing source code we have enable 
addcallback method for twitter too. user can add their own call backs fro 
twitter.

please let us know if still face any issues. we are expecting the same problem 
with facebook ( fb: connect) , currently we are checking it.

Original comment by vineet.a...@3pillarglobal.com on 19 Apr 2013 at 11:15

GoogleCodeExporter commented 8 years ago
hi, issue no.54 is related to new jar , you can expect the same problem in 
socialauth android 2.0 . we are currently fixing it.

Original comment by vineet.a...@3pillarglobal.com on 19 Apr 2013 at 11:16

GoogleCodeExporter commented 8 years ago
Even after adding the same callback URL that is on my twitter app site like 
this:

mSocialAdapter.addCallBack(Provider.TWITTER, "myURL");
mSocialAdapter.authorize(getActivity(), Provider.TWITTER);

where "myURL" is the actual callback URL (same as the website URL) I am using 
on the twitter developer app account.

Still I get the 401 error.

I'm using your 2.1.jar, from issue 48.

Original comment by matej.di...@gmail.com on 19 Apr 2013 at 12:35

GoogleCodeExporter commented 8 years ago
Thank you for your replay  The issuse i fixed.  I changed the callback URL from 
"twitterapp://connect"  to the callback url of my own application account . it 
work .......     

Original comment by luoshaoD...@gmail.com on 19 Apr 2013 at 1:58

GoogleCodeExporter commented 8 years ago
Thanks luosshao 

CLosing this issue.

matej , if you are still facing the issue, please open a new issue.

Original comment by vineet.a...@3pillarglobal.com on 22 Apr 2013 at 4:39

GoogleCodeExporter commented 8 years ago
Hi Vineet u r doing great job. I am facing the same problem with FB, and 
google, as many people faced with twitter.

Original comment by androidp...@gmail.com on 23 Apr 2013 at 9:49