tomdroid-dev team mailing list archive

[Benoit Garret <benoit.garret_launchpad@xxxxxxxx>]

Hey,

On Mon, Nov 9, 2009 at 11:01 PM, Sandy Armstrong
<sanfordarmstrong@xxxxxxxxx> wrote:
> On Mon, Nov 9, 2009 at 1:36 PM, Benoit Garret
> <benoit.garret_launchpad@xxxxxxxx> wrote:
>> I tested U1 with the patch you provided below (which should be the
>> only changes required to support oauth 1.0a). You're absolutely
>> correct in your assumption that Tomdroid is handling the tomdroid://
>> url, that's why another instance seems to be started (we should only
>> show the popup on the first run). I get the following exception when
>> trying to do the last part of the auth process:
>>
>> OAuthExpectationFailedException: Request token or token secret not set
>> in server reply. The service provider you use is probably buggy.
>
> That is the same exception I got, and tried ignoring, with
> unsatisfactory results.  :-)  I'd really like to see the response sent
> by U1 here...copying Signpost source directly in to Tomdroid bzr would
> allow debugging deeper into Signpost, right?

I made a few commits today:
* the expectation failed exception is a known problem in signpost:
http://code.google.com/p/oauth-signpost/issues/detail?id=20#c8. I
committed a hack which should fix the issue while we wait for a proper
fix from upstream.
* the notes api url was hardcoded, I'm now GETting the proper resource
from the server.

Syncing with U1 now works (for me) but more feedback is welcome ;-) .