Fix 400 Unable to Parse JSON for Google OAuth #1079
Conversation
|
I have a website that just went to production. I'm getting told iPhones are getting 400s when using Google auth. Is this related? |
|
error code is generated by application on server side and it can be anything 400 or 405. Underlying problem is additional field clientId. so if you're parsing oauth response from google without considering this additional field your code will fail. Error code is less important, it's really upto to what you implement on server side when parsing fails. |
|
It appears this is isolated to Safari on iOS. I'm still investigating. |
|
additional field name is "state" as shown in the pull request. Pull request only fixes java server backend, if you're using another server technology, then you will have to patch it accordingly. Pull request fixes the problem on server side, it has nothing to do with browser. So your issue is not related to this issue. |
Google response contains state field, server throws 400 - Unable to process JSON. adding this field to payload classes fixes the problem.
{"code":"","clientId":"**","redirectUri":"http://localhost:3000","state":"aeanx8630v"}