FirebaseAuth Twitter login flow on iOS

[XuanTung95]

Description

When using FirebaseAuth 10.13.0 on iOS app for Twitter login.

• iPhone XS
• iOS 16.5.1
• X app: 10.0

Actual:

• Open Twitter app before
• Click Twitter login button on My app -> Open login twitter web page
• Input wrong username/password
• Click Sign In -> It open Twitter app and asks for login. After I login, it stays on Twitter app and does nothing.

Expected:

• Could you make it more user friendly? If it open Twitter app, at least it should be able to complete the login flow.

Reproducing the issue

No response

Firebase SDK Version

FirebaseAuth ~> 10.13.0

Xcode Version

14.3

Installation Method

CocoaPods

Firebase Product(s)

Authentication

Targeted Platforms

iOS

Relevant Log Output

No response

If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[rizafran]

Thanks for reporting this, @XuanTung95. I was able to reproduce the issue. I observed that when I tried to sign in using the wrong username and password then using the correct credentials, the link changed from api.twitter.com/... to twitter.com/... With this, it seems like the API path was broken due to the transition from Twitter to X. I'll inform the engineers about this and will let you know if there's an update.

[aiFigueiredo]

FYI: I'm also having issues with an account with 2-factor auth. After authenticating, I get sent to twi... cof cof x's home page on the webview instead of the callback

EDIT: without two factor auth, it works as expected

[Evet7]

Same issue I'm experiencing ^

[rizafran]

Hello, per checking, this issue has been fixed in our backend. I also tried to reproduce it, and I'm now able to login. That being said, I'm going to close this ticket, but feel free to comment if you're still encountering the issue. Thanks.