Abdul Rehman Talat

Running into this issue myself, did you ever find a work around to this?

Hi @xiaoyijun , thank you for your response. But this distrupts the Expo development process. As Expo's offical [Expo Go](https://expo.dev/go) app uses this scheme. In Expo, for managed workflow apps,...

Any update on this?

@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...

> @artalat > > Thank you for providing the demo app. I ran a test locally and identified the issue. It is because of the strict [Cross-Origin-Opener-Policy](https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html#cross-origin-opener-policy-coop) set on Logto....

@simeng-li I have tried both cloud and self-hosted versions. Same issue. As for expo, I don't think they provide the functionality to do this without popup.

I have verified the fix and can confirm it works. Thanks for the quick resolution. How does that your release cycle work, ie when should I expect it to be...

> Did you add scopes to your resource `https://api.mevris.app`, add the scopes to a user role and assign the role to your end user? After that, you also need to...

# Example Opaque Token Here both resource & openid scope are sent. ## Auth Request ``` /oidc/auth?code_challenge=DFXpT_qX8BbHx9ZFJ1g4x11XOAGpuVTDYQEnegethIs&resource=https%3A%2F%2Fapi.mevris.app&code_challenge_method=S256&prompt=consent&redirect_uri=http%3A%2F%2Flocalhost%3A19007&client_id=gthwi145jrqgqw7itehxz&response_type=code&state=q06pjx36MH&scope=openid%20profile%20email%20offline_access ``` ## Auth Response ``` { "type": "success", "error": null, "url": "http://localhost:19007/?code=KkGRGSXph2S7ra5PzEgAdjDql2c0NLeCUszioYJ7QB-&state=q06pjx36MH&iss=http%3A%2F%2Flocalhost%3A3001%2Foidc", "params":...

Im not using any official SDK, developing in expo ```ts import * as React from 'react'; import { Button, Text, View } from 'react-native'; import * as AuthSession from 'expo-auth-session';...