The first OAuth failure happened on August 14. I had just successfully posted a few (three or four) tweets, and the fifth one failed. These were all in a row - no messing around in settings, no switching to other apps. Just "Read article, tweet, read article, read article, read article, tweet, read, tweet, read, read, tweet, read, tweet, read, OAuth-non-tweet"
These instructions that Brent Simmons gave for a similar problem temporarily resolved the issue, but after a few more successful tweets it returned to the OAuth problem.
# Still seeing it #
I tried again about 10 minutes ago, and the problem continues.
# Other things attempted #
In attempt to disrupt potentially fouled caches, I've also tried changing the Twitter password, and using the new password in NNW. It goes directly to the OAuth error.
For good measure, I again deleted the app, reinstalled from the App Store, re-synched with Google, and re-entered authorization details. Straight to OAuth error.
I've also attempted to post to a different Twitter account, and was sent straight to the OAuth error.
I've also tried switching to Wi-Fi only, and to Cellular Data only, in case Twitter was annoyed at my IP address.
# One more thing #
It was present when I was originally able to tweet, so I infer it had auto-setup when I authorized tweets in-app. It was present when the first OAuth failure happened. It was present after the first (temporarily helpful) reinstall. It was present after the second (unhelpful) reinstall.
It vanished, naturally, when I tried revoking access. But since then it has not reappeared, as I would expect after entering authorization information in NNW.
Do you know if there are any places that credentials get cached, on my phone or on the Twitter side, that wouldn't be cleared by deleting (using tap-hold, tap-the-X, confirm deleting all data) and reinstalling from the App Store?
On Thursday, August 16, 2012 7:40:24 PM UTC-4, Jack (Black Pixel) wrote:
I've been trying to reproduce this problem and haven't had any luck. Every post to Twitter goes through just fine.
I haven't seen any other reports of this, and I'm not aware of any current issues related to Twitter and OAuth.
When did the problem start? Are you still seeing it now?
Jack
The NetNewsWire Support Team
@nnw_mac
On Thursday, August 16, 2012 7:24:10 AM UTC-7, B.A. wrote:
I was successfully posting to Twitter in the paid version of NetNewsWire and, after making no changes to Twitter permissions, stopped being able to post. The following notification appeared:
Error posting to Twitter
Twitter reported an error: Could not authenticate with OAuth.
Following the
advice in this issue, I deleted NNW from my iPhone and reinstalled from the App store (I forgot that this would eliminate stars... mrph!).
After re-synching with my Google Reader account and re-entering Twitter user info, I was able to post to twitter again, but only four times, and then once again got the same error:
Error posting to Twitter
Twitter reported an error: Could not authenticate with OAuth.
For the sake of repetition (I'd lost the stars anyhow... mrph!) I again deleted the app from my phone, re-installed NNW from the app store, re-synched with Google, and tried to post to Twitter, and immediately got...
Error posting to Twitter
Twitter reported an error: Could not authenticate with OAuth.
For the sake of more repetition (Third time's the charm?) I again deleted the app from my phone, this time de-authorized NNW in Twitter for good measure, re-installed NNW from the app store, re-synched with Google, and attempted to tweet. Again, the immediate response...
Error posting to Twitter
Twitter reported an error: Could not authenticate with OAuth.
For the time being, I'm kludging around this by going NetNewsWire on my desktop and using the "News > Send to Twitter for Mac" menu item (which doesn't have a keyboard shortcut... mrph!), which makes the post without complaint (and without automatic URL shortening like on the iPhone... mrph!) but it's a suboptimal workaround.