-
-
Notifications
You must be signed in to change notification settings - Fork 364
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
bug: Expo client cannot use expo go redirect_uri #5632
Comments
Hi @xiaoyijun , thank you for your response. But this distrupts the Expo development process. As Expo's offical Expo Go app uses this scheme. In Expo, for managed workflow apps, development is done on Expo Go. So this is a problem. Besides, if the OS is not enforcing this limitation, why should Logto? |
@xiaoyijun let's discuss this next week |
Any update on this? |
@artalat, on which platform did you execute Expo Go? If it was iOS, you can define a custom redirect URI e.g. However, I'm afraid that this won't work on Android. Custom redirect URIs might not invoke the Expo Go app correctly on Android. To conduct testing on Android, you'll need to build an Android package instead of relying on Expo Go, and set the custom scheme in the The private use native client scheme is restricted by the OAuth2.0 spec.
Let me know if this helps. |
@simeng-li Thanks for your detailed response, apart from the hassle this causes, my point is if the OS/platform allows setting a scheme without a ".", Logto shouldnt enforce this restriction for those specific OS/Platforms |
Describe the bug
Expo Go app uses "exp" scheme for uri. For example:
exp://192.168.3.137:8081
. But logto use validation fails for this.Expected behavior
The client accepts such redirect_uris
How to reproduce?
Just try to set the example uri from the example given above.
The text was updated successfully, but these errors were encountered: