Having trouble signing in to your TweetDeck account?
If you are a longtime TweetDeck user, make sure you are signing in using the email address and password associated with your TweetDeck account (this might be different than the email address and password used for your Twitter account). Use your original TweetDeck account credentials unless you have opted to start using your Twitter account to sign in to TweetDeck.
Have your TweetDeck columns, connected accounts, or settings disappeared?
If you’ve signed in to TweetDeck and find your columns, accounts, and settings are gone, it’s likely that you started using TweetDeck before December 2013 and that you’ve signed in with your Twitter username and password instead of your unique TweetDeck account credentials.
Here’s how to get them back:
- Sign out of TweetDeck.
- Ignore the “Sign in with your Twitter account” form, and instead click the link to Sign in with your TweetDeck account.
- Sign in with the email address and password associated with your TweetDeck account.
Recent TweetDeck releases have made it possible to sign in using a Twitter username and password. If you signed up for a TweetDeck account prior to December 2013, you can opt to start using your Twitter account to sign in to TweetDeck, or you can continue to sign in using your TweetDeck email address and password.
Still having trouble with TweetDeck? Here’s what you should know:
For assistance with the TweetDeck app, please contact Support. However, we’ll need your help to collect the information necessary to solve these problems. If you’re experiencing any of the above or other issues, there’s useful data you can have ready for when you reach out to us, such as:
What version of TweetDeck are you using, and where?
Making TweetDeck work better is a primary reason we release new updates, so it’s important that you’re using the latest version. If you’re unwilling or unable to upgrade, it may limit our ability to assist you. All downloads for the below apps can be found at tweetdeck.com.
To find the version you are using:
- Click on the gear icon from the menu on the left and select Settings.
- From the General tab, you’ll see your version in the lower right corner in small type.
The latest version may differ on our various clients:
- Chrome app
- tweetdeck.twitter.com
- Mac app
- Windows app
Is it reproducible on tweetdeck.twitter.com?
If you’re using a TweetDeck app other than tweetdeck.twitter.com, it would be helpful for us if you could test your issue from the web app. This will let us know if the problem is affecting a specific app or the entire TweetDeck community.
Other info that will help us troubleshoot:
Often what’s going on at your computer is a big indicator of what’s causing the problem. If you can reproduce it within Chrome or Safari, there are tools that can give us information to diagnose.
Chrome users:
- Go to View > Developer > Javascript Console. This will open a screen with a lot of information; at the bottom will be a blinking cursor.
- Paste the following at the cursor: copy(JSON.stringify(TD.storage.store.jsonDump()))
- Press return (enter). This will copy some information that you can paste and send to us if we request it.
Safari users (slightly more complex):
- Go to Develop > Show Web Inspector. Make sure the Scripts tab is selected.
- Enable debugging (for this session only)
- At the bottom of the inspector, the second icon will open the console. Scrolling to the bottom, you’ll find a blinking cursor.
- Paste the following at the cursor: copy(JSON.stringify(TD.storage.store.jsonDump()))
- Press return (enter). This will copy some information that you can paste and send to us if we request it.
Now you’ve got a bunch of useful info that will help us troubleshoot your issue. In cases where the issue is caused by a certain action, we may also ask you to use www.screenr.com to reproduce the issue so we can see it firsthand. Any detail we can collect will put us closer to finding a solution.
For more information on Multi Channel Network’s and Twitter Help please check back weekly or subscribe here.
