Ios Twitter Kit 1.10.1 - TWTRLogInButton responds with -1012 error

[bonnell]

Thanks @GabeJacobs for sharing this. @michalhernas is it possible you’re hitting the same issue?

[michalhernas]

I don’t think so. I use Twitter app and Tweetbot and both of them work.
As I said before, it does not work on my phone that has 2 Twitter accounts configured but it works on my friends phone with 1 account. I believe this is main issue.

Scenarios I tried in Swift:

1. 1 twitter user on iOS, not authorized to my twitter app - WORKS
2. 1 twitter user on iOS, authorized to my twitter app - WORKS
3. 2 users on iOS - authorized to my twitter app - FAILS
4. 2 users on iOS - not authorized (access was revoked) to my twitter app - FAILS

Your example in Obj-C:

1. 2 users on iOS - authorized to my twitter app - WORKS (difference to Swift is that this one opens in-app browser and ask me to log in again to Twitter)

My dropbox link should work already: https://dl.dropboxusercontent.com/u/1824765/test-twitter.zip

Please check how it behaves here as I could reproduce it on this project.
Differences to Obj-C project you posted:

• It uses Swift
• I have TwitterKit imported using Pods
• I put UIButton on Storyboard and changed his callback later in viewDidLoad instead of using addSubview

I hope you can resolve this problem.
If you need more assistance please let me know. I am also right now in SF so I could even drop by to office (I would love to!)

[bonnell]

Thanks @michalhernas, I’m taking a look at your sample project and we’re also going to improve the logging around this error in our next release.

[jaredran]

@man_derson and I were wondering if instead of trying to repro, solve the route cause, and eliminate the -1012 error, you could provide a short-term solution–build into TwitterKit logic that catches the -1012 error and throws the user to the browser oauth experience.

[nedrockson]

I agree with @jaredran on this one. The framework should absolutely catch the case where there is invalid header data and ask the user to login again…

[bonnell]

Thanks both @jaredran and @nedrockson, I’m chatting with the team about improvements we could make here.

-Mike

[michalhernas]

So, my App was just rejected by Apple due to this bug.

Screenshot I got from them.

[jaredran]

Sorry…felt really weird hearting that. I just wanted to emphasize that this should be addressed.

[bonnell]

Thanks for letting us know @michalhernas, we just shipped out a new version of the Kit with updated logging. Can you grab the latest - 1.13.1 of TwitterKit and let me know what you see after in the console?

[petkanics]

This has been popping up amongst a large number of our new users. When they write in for support we have to tell them to go to the iOS settings menu and de-auth twitter, which is not a good solution. It would be great if the framework either caught the exception and routed to OAuth flow in the browser as @jaredran suggested, or if the framework provided some way to allow us to bypass the native auth and pass the user directly to browser based oauth. The sooner the better though, as we get reports about this bug every day in our app. Thanks.

[chaselatta]

It appears that this error is being returned because the user’s credentials are being corrupted in the system accounts framework. We do not have access to these credentials so we cannot automatically log the user in again. However, we have implemented a fix that will watch for this error code to be returned and prompt the user to go to the settings app to update their password using the -[ACAccountStore renewCredentialsForAccount:completion:] method. This prompt will take the user directly to the settings app to enter their password. We have also introduced a new error code TWTRLogInErrorCodeSystemAccountCredentialsInvalid which will indicate that this happened. The user can then update their system account, come back to the app and attempt to log in again.

We should be shipping an update which includes this fix in the next few days. We apologize for the inconveniences that this has caused.

[keighl]

That’s great news!

[mwaterfall]

Is the fix included in 1.14.0? There’s no mention of it in the changelog, however 13 days ago you said it will be shipping in the next few days. Cheers.

[bonnell]

@mwaterfall - the fix is live in 1.14.1

[niall]