Occasional 'Malformed response cannot be parsed' error with Twitter sign-in

[maryam-abdullah]

When signing in with Twitter, I sometimes get the error below:

POST https://www.googleapis.com/identitytoolkit/v3/relyingparty/verifyAssertion?key= 400 () [firebaseui] Internal error: {"error":{"errors":[{"domain":"global","reason":"invalid","message":"Malformed response cannot be parsed"}],"code":400,"message":"Malformed response cannot be parsed"}}

{ "error": { "errors": [ { "domain": "global", "reason": "invalid", "message": "Malformed response cannot be parsed" } ], "code": 400, "message": "Malformed response cannot be parsed" } }

And then, when I sign in again, it does successfully. Previously, everything was working fine.

Thanks in advance.

[bojeil-google]

Hey @maryam-abdullah I will relay your issue to the Firebase Auth backend team. Thanks,

[maryam-abdullah]

Thank you.

[ronnievsmith]

I had this same issue using Twitter Oauth, namely Malformed response cannot be parsed message.

The fix was for me to sign out of my Twitter account that has the oauth app then sign back in. That seems to be the fix for me.

[calchulus]

Also having the same problem

[bojeil-google]

This should be fixed.

[decent-developer]

Not fixed, just experienced this exact issue twice in a row while developing. This is my first project with Firebase, and I have to say this doesn't give me confidence in the product. How often do things like this happen?

[bojeil-google]

This is not the right forum for issues related to Twitter sign-in or other underlying communication issues between Firebase Auth server and Twitter OAuth endpoint. This open forum is for client side FirebaseUI related issues. Please open a bug with Firebase support. You will be asked to provide project related settings to help debug individual project related errors that are better resolved for a private channel.

[mapo-lp]

the issue is happening to me everyday .. somebody found a fix?

[snakajima]

It happens to me as well, not just occasionally but very often.

[narugami]

The best way is to stop using Firebase. I did.

[ljle]

This is happening to us on an app live in production with paying customers. @ronnieroyston's workaround didn't work, tried in various browsers and nothing. Clearing site data and cookies or incognito mode didn't work either, the Twitter Auth page isn't even reached, it just loads and goes back to the Firebase app and shows the "Malformed response cannot be parsed from twitter.com for OAUTH1_REQUEST_TOKEN" error. Even revoking access to the Firebase app from the Twitter account does not work.

Frankly, it's embarrassing this has been an issue for 4 years and there's no fix yet.

[Jood80]

any updates on this?

[avionics18]

Any updates?