Closed GoogleCodeExporter closed 8 years ago
You didn't write which steps lead to this, but I guess you turned OAuth off and
then typed Username AND Password?!
If so this currently doesn't work due to twitter.com restriction.
Please leave OAuth ON and press "Verify credentials"
Original comment by yvo...@gmail.com
on 7 Oct 2011 at 5:37
I decided to make user interface more clear:
1. Hide Password preference for OAuth
2. Disable OAuth preference for now (because the only supported provider -
Twitter.com - doesn't have other options).
3. For new account Change "Verify credentials" to "Add account" (like in GMail
app).
Original comment by yvo...@gmail.com
on 8 Oct 2011 at 3:42
I have tried both oAuth authentication and password authentication and I cannot
get the app to login.
With oAuth, I get to the authentication page and enter my credentials, and
after it goes back to the app, it tells me the credentials are for another
user...?
With password authentication, I get a connection error.
I see that you have made a commit to disable the password authentication
option, but that doesn't fix my problem with oAuth unfortunately.
Please help!
Original comment by Speeddy...@gmail.com
on 11 Oct 2011 at 12:29
I just had an idea that I tested which worked.
Open the browser and login to Twitter, then go to the app and remove your
username. Then hit verify credentials. It will then enter your username for you
in the app.
My problem with oAuth was that the username I entered in the app was entered
with proper case; that is, first letter capitalized. Twitter usernames are all
technically lowercase, so it wasn't taking my info.
Original comment by Speeddy...@gmail.com
on 11 Oct 2011 at 12:43
Ok, the problem with Credentials of another user was solved in v.1.2.0, see
Downloads link above.
Original comment by yvo...@gmail.com
on 11 Oct 2011 at 4:41
Fixed in Revision 4c229f818271,
please see v.1.2.1:
http://code.google.com/p/andtweet/downloads/detail?name=AndTweet-1.2.1.apk
Original comment by yvo...@gmail.com
on 12 Oct 2011 at 6:12
Original comment by yvo...@gmail.com
on 12 Oct 2011 at 6:13
Original issue reported on code.google.com by
rathna...@gmail.com
on 7 Oct 2011 at 12:25