Getting a 410 Error when logging into Twitter

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run Demo
2. Login via Twitter
3. Click Accept - get the error below

What is the expected output? What do you see instead?

An error occurred while executing 
http://api.twitter.com/1/users/show.json?user_id=xxxxxx
Request Parameters: 
oauth_consumer_key=xxxx&oauth_nonce=xxx&oauth_signature_method=HMACSHA1&oauth_ti
mestamp=xxxxxx&oauth_token=xxxxxxx&oauth_version=1.0&oauth_signature=xxxxxx=The 
remote server returned an error: (410) Gone.

What version of the product are you using? On what operating system?

v.2.3.1 / VS2012 / Win7

Please provide any additional information below.

http://api.twitter.com/1/users/show.json used auth 1.0 & has now been switched 
off by Twitter. Can I configure the path / OAuth version anywhere?

Original issue reported on code.google.com by pollyvin...@hotmail.com on 18 Jun 2013 at 11:56

[GoogleCodeExporter]

I too getting the same issue.
Response from twitter is as follows:

{"errors": [{"message": "The Twitter REST API v1 is no longer active. Please 
migrate to API v1.1. https://dev.twitter.com/docs/api/1.1/overview.", "code": 
68}]

Original comment by agarwala...@gmail.com on 21 Jun 2013 at 5:22

[GoogleCodeExporter]

I am able to fix it by referring to
Issue 177: Error with Twitter oAuth

Original comment by agarwala...@gmail.com on 21 Jun 2013 at 5:58

[GoogleCodeExporter]

Already in progress.. patch coming soon

Deepak

Original comment by deepakag...@gmail.com on 21 Jun 2013 at 5:59

[GoogleCodeExporter]

hi there ,

I am getting same error unfortunately. 

@Deepak: Thank you for you attention. When time can we test the patch ? Is 
there any prediction about this?

thanks.

Original comment by er...@pragmalinq.com on 21 Jun 2013 at 3:34

[GoogleCodeExporter]

i had seen it before, its because when socialauth tries to execute the feed it 
runs into issues..

Original comment by vishal.a...@gmail.com on 25 Jun 2013 at 5:31

[GoogleCodeExporter]

Please take a look at Issue 177, it was resolved with a small code change 
(single line)

Original comment by vishal.a...@gmail.com on 25 Jun 2013 at 5:32

[GoogleCodeExporter]

This issue was closed by revision r439.

Original comment by deepak.a...@3pillarglobal.com on 26 Jun 2013 at 8:58

• Changed state: Fixed