+Kev_MacD Posted June 15, 2013 Share Posted June 15, 2013 My twitter integration is not working. I log a cache (Windows 7 and both FireFox and IE) and go to "Connect with Twitter" on the log page - get redirected to the Twitter Authorization screen and Authorize Geocaching.com. It returns an error: An error has occurred: An error was returned from Twitter. Hitting the back button reveals the Twitter Error: Whoa there! The request token for this page is invalid. It may have already been used, or expired because it is too old. Please go back to the site or application that sent you here and try again; it was probably just a mistake. I have seen threads where the the solution is to revoke access from twitter and re-authenticate. I have done this several times, each time logging out and in again, then re-authorizing, and I still get the error. Help Appreciated. Thank you! Quote Link to comment
+FlavignyTeam Posted June 15, 2013 Share Posted June 15, 2013 I've the same issue with my Twitter account. In my Twitter profile, the Geocaching.com appears to be allowed but it doesn't work. Help would be appreciated. Quote Link to comment
Adya_Miriyana Posted June 15, 2013 Share Posted June 15, 2013 Same issue, not sure why.. Quote Link to comment
+alleepolleke Posted June 15, 2013 Share Posted June 15, 2013 (edited) Same isue. Who can help? Edited June 15, 2013 by alleepolleke Quote Link to comment
+1967kevin Posted June 15, 2013 Share Posted June 15, 2013 I'm having the same problem here, both on the website and on the Geocaching App on my iPhone. I've checked my Twitter account and can log in okay by going to twitter.com and it says geocaching.com is approved, but it won't allow me to tweet about any of my finds. Is there a way to rectify this? Quote Link to comment
+Mr. Wilson & a Mt. Goat Posted June 16, 2013 Share Posted June 16, 2013 Yep, same here, keep getting an error today. Quote Link to comment
+Smilin229 Posted June 16, 2013 Share Posted June 16, 2013 I'm having the same issue, 2 machines, and the mobile app Quote Link to comment
+DanPan Posted June 16, 2013 Share Posted June 16, 2013 Maybe the issue is caused by the fact that Twitter installed on 11 Juni a new version 1.1 of their API. Quote Link to comment
+_anea Posted June 17, 2013 Share Posted June 17, 2013 Also having this issue as of the 16th - was a new account, thought that may be why. My info is good. If it's a new version of the API that is the issue, perhaps a fix will be quickly forthcoming? Quote Link to comment
Moun10Bike Posted June 17, 2013 Share Posted June 17, 2013 I have confirmed this issue and entered a bug for engineering to investigate. Quote Link to comment
+alleepolleke Posted June 20, 2013 Share Posted June 20, 2013 Yes today it is working now!!! Quote Link to comment
+FlavignyTeam Posted June 21, 2013 Share Posted June 21, 2013 (edited) It seems to be fixed. It works for me. Thanks Edited June 21, 2013 by FlavignyTeam Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.