I have just met the same situation. I created my app with Read only,
then I used with that for a while. Later, I wanted to post, so I
switched to Read and Write. I kept re-requesting the access token, but
that didn't work.

The user still have "read-only" in their Setting/Connection tab.

Revoke, then authorize app again. Problem solved. (This make sense,
because user didn't give app the permission to write at first place.)

Hope this helps.

On Apr 23, 8:17 pm, Jeremy <jehe...@gmail.com> wrote:
> Hi all!
> I am having an issue with one of my apps. I set it up correctly I
> think, when I do tests through the API console 
> onhttp://dev.twitter.com/console,
> it posts just fine, and my app has read/write access level.
> However on my site, whenever I try to post a new tweet, the tweet
> process seems to go without any error messages, but nothing gets
> posted on my twitter account.
> I have checked it with Firebug, there is in fact an error, I get a 401
> Unauthorised status forhttps://api.twitter.com/1/statuses/update.json.
> It says "Read-only application cannot POST".
> I consequently changed my app settings, and indeed it was read only at
> first, but even after changing it to read/write, the problem remains.
> Any idea where it could come from? What can I do to solve the issue?
> Thank you!
> --
> Subscription 
> settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en

Reply via email to