Skip to main content

Troubleshooting Twitter @Anywhere's write permissions

With the recent launch of @Twitter's @Anywhere API there have been a number of developers having issues with the follow button and the Tweet Box not working. This stems mostly from a bug where new applications created on dev.twitter.com would default to read only access.

If are having problems using @Anywhere try this simple step by step guide.

  1. Check that your application has "Read and Write" as the "Default access type". If not edit your application settings so it does. You can do that on https://twitter.com/apps.
  2. Check that your @Twitter account's access token for said application has "read and write access". If not revoke access and re-authorized from the website you are testing @Anywhere from. You can find out the access type on https://twitter.com/settings/connections.
  3. Delete your cookies. Specifically the "twttr_anywhere" cookie for the domain hosting the @Anywhere code. You can read more about clearing your cookies https://www.google.com/support/accounts/bin/answer.py?hl=en&answer=32050
Have you had any other issues with @Anywhere? What solutions have you had?

Comments

  1. I have an issue but not a solution yet. On firefox 3.6.3, once your initialise the twitter anywhere object and the Iframes are created, the page becomes slightly wider. this creates a scrollbar for side scrolling which is a bit annoying

    ReplyDelete
  2. Sounds like you are putting the @Anywhere code somewhere where the inserted iframe is wider then the element it is being inserted into. Try playing with your CSS.

    ReplyDelete

Post a Comment

Popular posts from this blog

Sync is currently experiencing problems

Update : I now recommend you install Google Chrome  and  disable  the built in Browser as it supports encrypting all synced data. After picking up a gorgeous  Galaxy Nexus yesterday I was running into an issue where my browser data wasn't syncing to the phone. After a little Googling I found this is commonly caused by having all of my synced Chrome data encrypted instead of the default of only encrypting the passwords. These are the steps I went through to get my dat syncing again without losing any of it. The exact error I was getting was "Sync is currently experiencing problems. It will be back shortly." In Google Chrome open the personal stuff settings page by clicking this link or by opening the wrench menu, and click on "signed in with example@gmail.com".  Hit "disconnect your Google Account" to temporarily disable syncing from your browser. Visit the Google Dashboard and "Stop sync and delete data from Google". I waite

A month of Flutter: a look back

Originally published on bendyworks.com . This is it. 31 blog posts in 31 days. Writing  a month of flutter  has been a ton of work but also lots of fun and a good learning experience. I really appreciate how supportive and and positive everyone as been. Publishing experience For the series I've been posting on  bendyworks.com ,  DEV ,  my personal blog , and  Medium . After publishing to these sites, I would put the Bendyworks link on  Twitter ,  Reddit , and the  Flutter Study Group Slack . Posting to DEV was easy as they use Markdown just like the Bendworks blog. DEV also has built in support for a  series of posts  so it's easy to read the entire series. I did have to manually upload any embedded images. DEV also has a number of  liquid tags  for embedding things like GitHub issues that I didn't make as much use of as I should have. Blogger is rich text so it was easy to copy/paste the rendered posts. This would hotlink all the images though so I had to rem

A month of Flutter: the real hero animation

Originally published on bendyworks.com . For the last post before the month's wrap up tomorrow, I wanted to do something more fun: use a  hero animation between the home page list and the individual post page. When I first implemented the  Hero  animation it never worked going back from a  PostPage  to the  HomePage . The reason was that  HomePage  would get rerendered and that would  generate new fake posts . So I moved the fake data generation up a level to  MyApp  and pass it into  HomePage . This is more realistic as going to the  HomePage  shouldn't request the  Post s every time. HomePage ( title: 'Birb' , posts: _loadPosts ( context ), ) The  PostPage  implementation is a simple  StatelessWidget  that takes  Post  and renders a  PostItem . This will become more complex as things like comments and likes are implemented but works for now. class PostPage extends StatelessWidget { const PostPage ({ Key key , @required this