Turns out that the bug was in a different place - what I get for
"from_user_id" via search is not the user's ID but some other ID. I
had not looked at the notes for "search" or otherwise I would have
known about this defect. So I was happily issuing friendships/create
requests using the invalid ID
It also works using twitter-async. You can run the unit tests.
http://github.com/jmathai/twitter-async/tree/master
On Oct 5, 11:43 pm, Fahim wrote:
> I have tested using three different libraries - one is MPOAuth, the
> other one is the PHP library linked to via the Twitter API wiki and
> the
I have tested using three different libraries - one is MPOAuth, the
other one is the PHP library linked to via the Twitter API wiki and
the last one is my own custom Objective-C framework. None of them work
- but only for the friendships/create method. The code works fine for
other methods, as I m
I have tested friendships/create using my python libraryvia oauth and
works fine.
My guess is you are not generating a valid oauth request (ex. invalid
signature).
Could you provide a link to the code you are trying and what libraries
you are using? It would help
others in diagnosing your issue.
Nobody knows anything about this? I've tried three different OAuth
frameworks (one in PHP and two in Objective-C) and all of them return
a "Page not found" for a /friendships/create.json
Is anybody on the Twitter team able to confirm or deny whether this is
a bug?
Regards,
Fahim
On Oct 4, 11:2
