We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
redirectURI
I have two environments that I want to try with Auth0 and interchange between them at runtime. So that PROD and DEV flags are runtime values.
But whenever I call auth0.webAuth.authorize(...) using the two different credentials.
auth0.webAuth.authorize(...)
The first time it works, but when I switch to the other one, it still uses the same redirectURI but with some different credentials.
The modal pop-up still shows the same domain that I used the first time.
I'm not sure if it's caused by the iOS's webview? Or is it React Native? Or is it Auth0?
No repro. I'll try to make a minimal example in a while.
No response
3.2.1
0.74.1
iOS
17.5
The text was updated successfully, but these errors were encountered:
I am facing the same issue @TPLCarloTaleon were you able to resolve it
Sorry, something went wrong.
No branches or pull requests
Checklist
Description
I have two environments that I want to try with Auth0 and interchange between them at runtime. So that PROD and DEV flags are runtime values.
But whenever I call
auth0.webAuth.authorize(...)
using the two different credentials.The first time it works, but when I switch to the other one, it still uses the same redirectURI but with some different credentials.
The modal pop-up still shows the same domain that I used the first time.
I'm not sure if it's caused by the iOS's webview? Or is it React Native? Or is it Auth0?
Reproduction
No repro. I'll try to make a minimal example in a while.
Additional context
No response
react-native-auth0 version
3.2.1
React Native version
0.74.1
Expo version
No response
Platform
iOS
Platform version(s)
17.5
The text was updated successfully, but these errors were encountered: