search

cezarsa / silver_bird

Extension to access your Twitter from the Google Chrome browser.
http://cezarsa.github.com/silver_bird/
MIT License
286 stars 87 forks source link

Repeated calls to auth_token, interface never shows up #317

Open mindsocket opened 13 years ago

mindsocket commented 13 years ago

I used to use Silver Bird a lot. I have my systems synced (2 x linux, 1 x windows) but lately the windows install (Chrome 15) has not been working.

Bringing up the background.html network information in the developer tools shows that the extension goes into an infinite (?) loop of hitting twitter's request_token url. Each request ends up with a status of "cancelled" for some reason.

I've tried reinstalling, using a different chrome profile and changing proxy settings, but nothing seems to work.

Any ideas?

mindsocket commented 13 years ago

I was able to resolve this by pointing to a different proxy. However, I believe the twitter_lib.js handling of this is screwy. It gets stuck in a retry loop. In twitter_lib.js, the makeRequest has an ajax call that on success calls requestTokenCallback with the xhr in the tryAgain parameter position. I think a false param needs to be inserted here. This avoids the loop and reports an error. The error message that comes up is misleading because the problem is to do with the proxy mucking things up (response code is success but data=""). Hope this info helps :)

snowraptor commented 13 years ago

On Linux, I have a similar auth problem:

SilverBird acts as it was not authorized and when I click on it I'm redirected to Twitters wuthorize app page.

The PIN appears briefely, being replaced by a message notifying that It was successfully authenticated.

Of course, silverbird was already authorized to start with.

Then the plugin loads, this message is shown on the console:

[5973:6141:5719825015:ERROR:x509_certificate_nss.cc(797)] CERT_PKIXVerifyCert for twitter. com failed err=-8181

EDIT: The problem I described is solved by removing the extension, revoking acecess on twitter options, closing chromium (not sure if this step is necessary), then reinstalling the extension and only then authorizing it on Twitter. If the extension ins reinstalled without revoking access on Twitter options, the problem pesists. I am not sure how to reproduce this issue.