Anybody else getting "authentication failed" with the latest version of Seesmic? Seems their update to use the new twitter api broke authentication. I've followed up with them, and haven't received a solid reply. It appears I'm not the only one, but I don't know what they're using. I've checked all my settings in the OS and I'm not blocking anything coming from the browser or client. Just thought I'd throw it out there. Not sure if it's SS or Seesmic (I'll bet seesmic)
I'm running:
SS5.4, 0.9 GHz, LV
A piece of my log if it helps at all:
06-21 17:09:55.790 W/System.err(10271): oauth.signpost.exception.OAuthExpectationFailedExc eption: Authorized request token or token secret not set. Did you retrieve an authorized request token before?
06-21 17:09:56.087 W/System.err(10271): at oauth.signpost.AbstractOAuthProvider.retrieveAcces sToken(AbstractOAuthProvider.java:91)
06-21 17:09:56.087 W/System.err(10271): at com.seesmic.ui.Welcome$TwitterRetrieveTask.doInBac kground(Welcome.java:1498)
06-21 17:09:56.102 W/System.err(10271): at com.seesmic.ui.Welcome$TwitterRetrieveTask.doInBac kground(Welcome.java:1461)
06-21 17:09:56.102 W/System.err(10271): at com.seesmic.common.LoadingTask$2.call(LoadingTask. java:215)
06-21 17:09:56.102 W/System.err(10271): at java.util.concurrent.FutureTask$Sync.innerRun(Futu reTask.java:306)
06-21 17:09:56.118 W/System.err(10271): at java.util.concurrent.FutureTask.run(FutureTask.jav a:138)
06-21 17:09:56.126 W/System.err(10271): at java.util.concurrent.ThreadPoolExecutor.runWorker( ThreadPoolExecutor.java:1088)
06-21 17:09:56.126 W/System.err(10271): at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:581)
06-21 17:09:56.149 W/System.err(10271): at java.lang.Thread.run(Thread.java:1019)

LinkBack URL
About LinkBacks
Reply With Quote