Since scribe 1.3.0 there's adebug mode you can use to help yourself (and others) troubleshoot.

Usage is simple, just add thedebug() call while you're creating the service like this:

final OAuth10aService service = new ServiceBuilder("6icbcAXyZx67r8uTAUM5Qw") //apiKey here                                .apiSecret("SCCAdUUc6LXxiazxH3N0QfpNUvlUy84mZ2XZKiv39s")                                .debug() // here!                                .build(TwitterApi.instance());

Debug will output toSystem.out some interesting information that will help you find what's wrong.

Also, you don't necessary have to use the default output, since there's another method that accepts anOutputStream to send the debugging information, just in case. It's calleddebugStream and, as previously noted, takes anOutputStream of your choice.

These are useful weapons to fight the OAuth corner cases, I hope you find them as useful as I do. :)