search

fernandogdj / microblog-purple

Automatically exported from code.google.com/p/microblog-purple
GNU General Public License v3.0
0 stars 0 forks source link

Failed to validate oauth signature and token #209

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. create account logins
2. attempt to login

What is the expected output? What do you see instead?
Failed to validate oauth signature and token

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

Please provide any additional information below.

ever since i tried to it with 0.2.4 the onto 0.3.0 (complete removal of 0.2.4 
then make the 0.3.0 from source)

don't know where or how to get any debugging log or what not so this is the 
best info i can give.

Original issue reported on code.google.com by maximus....@gmail.com on 25 Aug 2010 at 9:57

GoogleCodeExporter commented 8 years ago 
Please run pidgin with -d flag

pidgin -d > debug.log

And attach debug.log here

Original comment by somsaks on 26 Aug 2010 at 4:53

GoogleCodeExporter commented 8 years ago 
heres the log, a text file called pidgin-twitter

Original comment by maximus....@gmail.com on 31 Aug 2010 at 5:37

Attachments:

GoogleCodeExporter commented 8 years ago 
I was having the same issue. With microblog-purple version 0.3.0 and Pidgin 
2.6.3.

What fixed it was an update to the latest version of Pidgin (2.7.3). Works 
great now!

Debug log attached from my old pidgin install if it would be any use...

Original comment by ErikGran...@gmail.com on 13 Sep 2010 at 8:29

GoogleCodeExporter commented 8 years ago 
(file actually attached this time)

Original comment by ErikGran...@gmail.com on 13 Sep 2010 at 9:18

Attachments:

GoogleCodeExporter commented 8 years ago 
maximus:
In pidgin, open the accounts menu, select the TwitterIM account, in the submenu 
click on "remove access credential".
Then try to reconnect.

Original comment by andresen.nils@gmail.com on 15 Feb 2011 at 7:50

GoogleCodeExporter commented 8 years ago 
@maximus: Does the problem still persist?

Original comment by andresen.nils@gmail.com on 13 Sep 2011 at 10:38

GoogleCodeExporter commented 8 years ago 
I still have this issue.  The problem is not present on windows, but it is 
present on linux.

Original comment by n8b...@gmail.com on 22 Oct 2011 at 6:09

GoogleCodeExporter commented 8 years ago 
Scratch that, I've fixed the problem.  If your system clock is inaccurate, 
you'll get this error.

Original comment by n8b...@gmail.com on 22 Oct 2011 at 6:18