This is very Java/Android specific code here which makes it difficult for a generalist to provide assistance to you. There are quite a few reasons for an OAuth signature to fail validation, and many libraries abstract the OAuth process to a point where you cannot clearly determine what aspect of the request is at fault.
It would appear the callback scheme here is the protocol/scheme used for the callback to hit (which likely needs to be registered & understood by the device) and the callback URL is the path in your application that can understand and consume the HTTP callback it will receive. If you can provide more basic/primitive details on how this is failing, at the HTTP level or examples of your signature base strings (generally made difficult to obtain by overly-complex OAuth libraries) we can help you with much more ease. Finally, often OAuth failures are for really simple reasons: the clock being off on the device for example. Do you have much experience with OAuth outside of the usage of this library? @episod <http://twitter.com/episod> - Taylor Singletary On Fri, May 27, 2011 at 1:23 PM, marcio <[email protected]> wrote: > Ive been told its a twitter api problem because only changing the > key/secret causes the error. > > -- > Twitter developer documentation and resources: https://dev.twitter.com/doc > API updates via Twitter: https://twitter.com/twitterapi > Issues/Enhancements Tracker: > https://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > https://groups.google.com/forum/#!forum/twitter-development-talk > -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
