Select to view content in your preferred language

Twitter Add-in Error

2047
9
09-29-2011 11:12 AM
R__CraigHolmes
Emerging Contributor
I successfully had the Twitter add-in working on version 1700, couldn't get it to work on 1750 so I went back to 1700 and just continue to get "Sorry, the application could not access Twitter at this time.  Please try again later."

I wonder if this is just coincidental to perhaps a rate limit from ip?

Fiddler doesn't really give me an error. Does the oauth key expire?
0 Kudos
9 Replies
R__CraigHolmes
Emerging Contributor
I managed to dig up a couple of possible errors in Fiddler:

WININET CACHE INFO ============
This URL is not present in the WinINET cache.

* Note: Data above shows WinINET's current cache state, not the state at the time of the request


and

ReadResponse() failed: The server did not return a response for this request.

So the Oauth key tied into AGX is not validating.  How to I get a new one when I am not hosting the Twitter developed application? ESRI is.
0 Kudos
AndreiIvanov
Deactivated User
Craig, we'll review it and post updated add-in if necessary. Thank you for bringing this to our attention.
0 Kudos
R__CraigHolmes
Emerging Contributor
Any movement on this?
0 Kudos
AndreiIvanov
Deactivated User
Craig, I am checking on it. The person who is responsible for this add-in didn't have a chance to take a look at it.
0 Kudos
AndreiIvanov
Deactivated User
Craig, we've checked add-in over here, and nobody had the issue logging in. Log into your account on twitter.com, check that you didn't revoke ArcGIS Explorer from your trusted application, and just make sure your credentials work on twitter as well. Hope it helps!

I am using add-in successfully on 1750:

[ATTACH=CONFIG]10017[/ATTACH]
0 Kudos
R__CraigHolmes
Emerging Contributor
No.  That's just it.  I get the attached...choose authorize and then Twitter just doesn't authorize AGX for me.
0 Kudos
R__CraigHolmes
Emerging Contributor
For those on the edge of your seats for a solution to this......

After some digging I found out that this is indeed a Twitter API issue not AGX.
My issues were actually 2 fold.

1.Twitter will not "always" allow an application access to an account once it has been revoked therefore you have to make a new Twit account.

2. The OAuth2 page was not using my default Chrome for the handshake but using a stone age IE6.  Installing IE8 fixed that.
0 Kudos
BruceJumper
Emerging Contributor
I am having this issue. My Twitter has authorized the use with Explorer. Every time I try and connect with Explorer it says Sorry the application is not available at this time and it says try again later. I have tried to use multiple machines but none work. What do I need to do?
0 Kudos
BruceJumper
Emerging Contributor
attached is the error. it occurs as soon as you click sign in.
0 Kudos