Plus now I found this :(
http://stackoverflow.com/questions/5962526/how-to-connect-twitter-client-application-in-android
On Fri, May 27, 2011 at 9:43 PM, marcio quique...@gmail.com wrote:
Yes I have. I read it 2x and I just read it again once more. I understand
about 25%. But if I use a
ok I got it...my app was actually client type, but even though its a client
native app on android, it has to be browsable for the callback url to work,
EVEN THOUGH the callback_URL you configure on dev.twitter.com is just for
looks cause you end up redirecting to your app anyway. :) Thx for
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:
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
I placed the code here:
git://gist.github.com/996219.git
or
https://gist.github.com/996219
Here is the eclipse/logcat error:
05-27 14:40:25.964: WARN/System.err(441):
oauth.signpost.exception.OAuthCommunicationException: Communication with the
service provider failed:
All other concerns aside, this error here indicates that for some reason
your code is not able to reach out to
api.twitter.com/oauth/request_tokenvia SSL.
Can you provide a brief overview of the settings you've made for your keys
on dev.twitter.com? Application type (should be Client with a
@Anywhere settings...but there is nothing there.
API KEY (which incidentally is the same as the OAuth Key)
Callback URL is empty because i chose Client type.
General Access Level : Read Write Permissions
OAuth 1.0 Settings
Consumer Key
Consumer Secret
Request Token URL
Access Token URL
The sample code you're showing me uses a callback (a custom URI callback
URL) so you'll need your application settings to client (Desktop restricts
dynamic callbacks). Just put a placeholder HTTP-based URL in the callback
field, select the Client radio button and save your app -- it might be the
I didnt understand that. Do you mean i have to change something in my
dev.twitter.com Application Details or in my code?
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker:
On dev.twitter.com -- your app needs to be configured to handle dynamic
callbacks like the code you're using utilizes.
Have you done much reading on our OAuth implementation?
http://dev.twitter.com/pages/auth -- it helps to have a bit of background
knowledge on the underlying processes, even if
Yes I have. I read it 2x and I just read it again once more. I understand
about 25%. But if I use a callback URL I need to change my application to
browser instead of client? But what do I enter as callback URL? Because it's
still a client based app so it really needs to return to my app,
11 matches
Mail list logo
