Skip to content
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

"Invalid URI or Environment" in Blazor WASM app #324

Open
codyaweber opened this issue Jan 23, 2024 · 1 comment
Open

"Invalid URI or Environment" in Blazor WASM app #324

codyaweber opened this issue Jan 23, 2024 · 1 comment

Comments

@codyaweber
Copy link

Attempting to instantiate a new OAuth2Client in a Blazor WASM app always throws an "Invalid URI or Environment" error, while the exact same instantiation succeeds in a normal Blazor app. This occurs in the GetDiscoveryDoc method. The response from the discoveryClient.Get() call in that method has the following error:

Error connecting to https://developer.api.intuit.com/.well-known/openid_sandbox_configuration: Cannot wait on monitors on this runtime.

I understand this is due to the single threaded nature of WASM, but it'd be nice if this package worked in WASM, or if not, at least had a note saying that it is not intended for use on that runtime.

@codyaweber
Copy link
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant