-
Notifications
You must be signed in to change notification settings - Fork 209
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
Not working after upgrade to React Native 0.60.x #230
Comments
Seems that this code is throwing, and then the error is being muted due to the catch statement trying to gracefully resolve (...should this be a graceful failure?) The request is failing here: With the error at Has |
AH! Looks like there is a new issue in react-native: |
@bneigher it seems like a bug on the latests react-native version. What if you move to a previous patch? e.g. 0.6.0, 0.6.1 or 0.6.2. Is the issue still happening? |
Yep thats what I found. Downgrading works, but I'm cool with the fix referenced in my comment above |
👍I don't think we should be changing that from the SDK side. I don't even know if adding that today would break older React Native versions.. And since this SDK doesn't specify a react-native version, I think it's best to delegate that decision to the users. Probably the next RN patch fixes it. |
Description
I seem to be running into a runtime issue with the functionality of react-native-auth0 after upgrading from RN 0.59.9 to RN 0.60.3.
This seems to only have an effect on the simulator.
Seems that there is an issue with handling the responses made after HTTP requests are made by this sdk. To be clear - I can see the requests being sent with the correct parameters, but the response preview doesn't show any data in chrome debugger, the promise resolves successfully, but there is an error:
AuthError: unknown error
After adding some debugging to the src, it looks like the http requests don't contain a json property?
Prerequisites
Environment
Please provide the following:
Reproduction
Again - this only affects the simulator apparently.
Anyone else seeing this?
The text was updated successfully, but these errors were encountered: