So far I’ve only seen two issues causing this. One is the callback URL not being set. If this is it, some people have had better luck deleting their Twitter App and starting over.
The other is having no HTTP transport option on your server. This is often the case for local dev environments where you may not have installed something like CURL. Most hosts won’t have this problem, but some low end shared hosts have definitely had configuration issues like this before.
Viewing 1 replies (of 1 total)
The topic ‘Could not recognize the response from Twitter’ is closed to new replies.