Issue Details (XML | Word | Printable)

Key: TFJ-149
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Yusuke Yamamoto
Reporter: Yusuke Yamamoto
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Twitter4J

OAuth fails with "Invalid / expired Token" after May 13, 2009

Created: 16/May/09 07:57 PM   Updated: 19/May/09 01:13 AM   Resolved: 19/May/09 01:13 AM
Return to search
Component/s: Core
Affects Version/s: None
Fix Version/s: 2.0.4


 Description  « Hide
After May 13, the API returns screen_name and user_id with the access token and Twitter4J fails to parse the return properly.
------
May 13, 2009
Fixed (REST): Background images uploaded via the API now take effect immediately (issue 451)
Fixed (OAuth): Using the authenticate method with force_login=true incorrectly returned the old users token.
There is still a known issue where the user is asked to accept the application each time. A fix is pending.
Feature (OAuth): When retrieving the access token via the access_token call the screen_name and user_id are returned as well.
------

Twitter4J fails with following error.
---------------
<?xml version="1.0" encoding="UTF-8"?>
<hash>
  <request>/statuses/update.xml</request>
  <error>Invalid / expired Token</error>
</hash>
---------------



Sort Order: Ascending order - Click to sort in descending order
Yusuke Yamamoto made changes - 19/May/09 01:13 AM
Field Original Value New Value
Status Open [ 1 ] Closed [ 6 ]
Resolution Fixed [ 1 ]