Open GoogleCodeExporter opened 8 years ago
Usually this is caused by Twitter not answering a request. The message is
definitely
mis-leading and needs to be addressed.
Original comment by keith.el...@gmail.com
on 7 Feb 2009 at 1:07
Original comment by james.deville
on 8 Feb 2009 at 4:56
Issue 213 has been merged into this issue.
Original comment by james.deville
on 8 Feb 2009 at 4:57
Issue 173 has been merged into this issue.
Original comment by james.deville
on 8 Feb 2009 at 7:46
Issue 151 has been merged into this issue.
Original comment by james.deville
on 8 Feb 2009 at 7:50
Issue 142 has been merged into this issue.
Original comment by james.deville
on 8 Feb 2009 at 7:55
Issue 133 has been merged into this issue.
Original comment by james.deville
on 8 Feb 2009 at 7:56
I'm merged Issue 213 .... did a Witty 2.1 install on my other tablet (ASUS R2H)
running Tablet XP and the issue did not replicate.
Given that, issue 213 should be closed - my issue is obviously machine specific.
Original comment by mmason
on 10 Feb 2009 at 6:27
Added a fix for some of these errors (Timeout related errors). Revision 461
Original comment by james.deville
on 24 Feb 2009 at 7:09
This issue occurs in version 2.1.2.0 but coinsides with the message that the
rate
limit has been exceeded at 100. What is a rate limit anyway?
Original comment by a...@harborcomputerservices.net
on 13 Mar 2009 at 5:55
Issue 198 has been merged into this issue.
Original comment by james.deville
on 31 Mar 2009 at 6:25
Issue 240 has been merged into this issue.
Original comment by james.deville
on 31 Mar 2009 at 6:27
Issue 234 has been merged into this issue.
Original comment by james.deville
on 31 Mar 2009 at 6:27
this also occurs if you enter the wrong password when logging in, which is
certainly
non-obvious
Original comment by troygoode
on 9 Aug 2009 at 3:08
1. It happens everytime I wake up my computer from sleep mode
2. Expected: no error window (my connection is waking up after few seconds),
Instead: Error message just after I logged back to my machine
3. Version 2.1.2.0
4. My machine: Vista Business 64-bit, 8GB RAM, Intel quad Q9550
Another Machine: Vista Home Premium 64-bit, 8GB RAM, AMD Phenom X4 quad 9650
Original comment by remi...@gmail.com
on 10 Aug 2009 at 3:13
I get the same trouble, but now Witty stops working after the error message
(and
microsoft tries to find a solution). If there is anything I can send to help
solve
this issue, please let me know.
Machine: Windows 7 RC x64, 4Gb RAM, Dell Inspiron 1545, v. 2.1.0.540
Original comment by miguel.m...@gmail.com
on 18 Oct 2009 at 2:25
BTW, removing and reinstalling does not solve the issue. Witty does not open
in my
computer at all.
Original comment by miguel.m...@gmail.com
on 19 Oct 2009 at 1:07
Cleaning the registry does not work either, now I am lost in what I can do so
Witty
runs as it used to. Apologies for the so many posts, hopefully it will help to
fix
the issue. Thanks!
Original comment by miguel.m...@gmail.com
on 19 Oct 2009 at 1:54
[deleted comment]
I get this error when I try to log in.
As I feared, looking at the requests, I see that Witty still does Basic auth
instead of OAuth... Twitter answers error 53 "Basic authentication is not
supported". Witty should make meaningful error messages instead of these
"unexpected error" that actually doesn't need to restart the software!
If the software is abandoned, you should state it clearly on the home page...
Original comment by PhiLho....@gmail.com
on 22 Sep 2010 at 4:01
Phil - There's another bug for OAuth, it's #271. If the software is abandoned,
we'll announce it. It's not. You're welcome to help. Work is in progress in the
new repo, here: http://wittytwitter.codeplex.com/SourceControl/list/changesets
Original comment by jongallo...@gmail.com
on 23 Sep 2010 at 2:26
install newest version.
Original comment by vegascom...@gmail.com
on 18 Mar 2013 at 4:48
Original issue reported on code.google.com by
toniac...@gmail.com
on 7 Feb 2009 at 1:04