> … Have you set up a callback URL with twitter (it doesn’t need to be a real URL, just needs to have a value)?
> … Have you made your Twitter app an “@Anywhere” app (whatever that means)?
Yes, I have done both.
>I’m moving testing onto a live site, just in case it’s “localhost” that’s the problem – twitter seems to be a stickler about which domains it will authorize requests from. Maybe that’s why the example recommends trying FB first.
I’ve tried doing the same thing with no luck. However, once you’re redirected to the callback.php file with that error, refresh and it tells you specifically what the issue is.
> no, no need to create a new key+secret. I’m getting the same response with my own set.
Too late, sorry!