-
Notifications
You must be signed in to change notification settings - Fork 214
Not working on Android 8.0 Oreo #165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
With 8.0, for me in OAuthManagerModule.java
receives a OAuth2AccessToken that looks more like a payload from a URL separated by ampersands (not Json) and the GSON parser crashes on receiving it in about line 404. Even if it were properly formatted Json, it would not contain the "user_id" that we need.
I backed down to 7.1 and avoided this crash. |
I'm seeing possibly the same issue on Android 6.0. Logcat:
I don't think it's Android-version specific. The code in question is:
and
so the issue is as @SailingSteve reports that the code is expecting JSON back and it's getting a querystring (x-www-form-urlencoded) instead. What I don't understand is how this ever worked -- https://developer.twitter.com/en/docs/basics/authentication/api-reference/access_token is clear that oauth tokens are returned as a querystring. So I must be missing something. (I think that 2a1c0fb#diff-9fc211ef231ecaa3ee7613d9696db4a1 is the commit which changed code to parse the response as JSON, instead of as a querystring.) |
(x-www-form-urlencoded), not as JSON, so signing in breaks as per fullstackreact#165. Correct this by catching the JSON parse error and falling back to extracting the parameters we need from the token instead.
Facebook login fails with "Sorry something went wrong" message
Google login just hangs after entering the password
The text was updated successfully, but these errors were encountered: