-
Twitter Auth problem in iOS7
An issue with the iOS7 upgrade process and Twitter:
I’ve seen this on 6 different friends’ devices this week alone: When you upgrade and restore (via iCloud at least) your Twitter accounts remain listed in your settings, but your Twitter password credentials don’t travel with you. From an app’s perspective, this means all your twitter accounts show up, but none of them will work when trying to make an API call. Here’s what the account list looks like in Tweetbot (I’ve already fixed two of the accounts):
And the error when I try to use a broken account:
How to fix (for users):
If a twitter app you use on iOS7 stops working because of this, you can fix it by re-entering your twitter passwords from the iOS Settings > Twitter screen. You’ll see the following error when you tap on the account:
Just say OK, enter your password, and you should be good to go!
How to fix (for iOS developers):
If you’re already handling the case where the request doesn’t return a 200, you’ll at least escape the endless spinner that users are seeing in Eddy (facepalm):
But one thing that may trip you up is that Twitter API v1.1 does not return a 401 Unauthorized in this situation, but a 400 Bad Request. So you have to watch for that and handle it appropriately, either by letting users auth through web oAuth, or asking them to fix the problem in iOS settings. I haven’t yet figured out a way of detecting whether it is a 400 because of this or some other problem, so if you figure that out please let me know.
This will be fixed in Eddy in 0.92 next week. Until then you can fix the problem by entering your password in iOS Settings.
-