You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The promise returned by webAuth.authorize() will consistently not complete when called immediately again after pressing cancel on the iOS permission popup (i.e. "App" want to use...). The issue is related to this if statement:
In reproduction situation both redirectURL and closeOnLoad are both falsy and the urlHandler will never be called so the promise being returned never completes.
What was the expected behavior?
The promise should always resolve or reject.
Reproduction
I can across this behaviour by automatically calling authorize again when the authorize promise rejects. Something like:
Widcket
added
bug
This points to a verified bug in the code
and removed
needs investigation
An issue that has more questions to answer or otherwise needs work to fully understand the issue
labels
Mar 18, 2022
Describe the problem
The promise returned by
webAuth.authorize()
will consistently not complete when called immediately again after pressing cancel on the iOS permission popup (i.e. "App" want to use...). The issue is related to thisif
statement:https://github.com/auth0/react-native-auth0/blob/master/src/webauth/agent.js#L44
In reproduction situation both
redirectURL
andcloseOnLoad
are both falsy and the urlHandler will never be called so the promise being returned never completes.What was the expected behavior?
The promise should always resolve or reject.
Reproduction
I can across this behaviour by automatically calling authorize again when the authorize promise rejects. Something like:
The returned promise from step 3 will never complete. When the timeout is increased to 1000 the problem does not manifest.
I can probably provide a reproduction scenario via the sample app if the above does not highlight the problem clearly enough.
Environment
2.13.0
N/A
N/A
ephemeralSession
is falseThe text was updated successfully, but these errors were encountered: