Thanks for this. We just ran into it.
On Jul 1, 7:26 am, Yusuke yus...@mac.com wrote:
Hi,
Twitter4J users are facing sun.security.validator.ValidatorException
as of July 1 GMT.
It looks to be an API side issue. Is it a known one?
It can be workarounded with -Dtwitter4j.http.useSSL=false
lifting of this, and
I'm not specifying a callback url when I request a token since I have
one in the application settings already. Do I need to specify the
callback URL anyway?
Thanks,
sb
the
callback url and adding state. I'll address that once this issue is
resolved.
Neel
On Jun 23, 10:46 am, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi sb,
I'm surprised that you're not getting the oauth_verifier in the OAuth
callback -- do you have an example of the complete callback
I should also note that I used to have the application registered as a
client and would get a verification code when it was like that. This
app is also registered as a normal app and not as an @Anywhere but
hopefully that doesn't make a difference..
sb
On Jun 23, 1:44 pm, sb teknos...@gmail.com
and adding state. I'll address that once this issue is
resolved.
I used to have this as a client application, and when doing that, I
would get a verification code in the browser that I could pass using
oauth_verifier. This worked fine. Does the app need to be registered
with @Anywhere?
Thanks,
sb
Hey guys,
It seems with twitter4j, I had to specify a callback url. When I did
this, I get a verifier. Not sure where the error lies. I'm using
twitter4j-core-2.1.2.
sb
On Jun 23, 2:03 pm, sb teknos...@gmail.com wrote:
Hi Taylor,
Thanks for getting back to me. I'm getting something like
