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
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.
The text was updated successfully, but these errors were encountered:
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 theGetDiscoveryDoc
method. The response from thediscoveryClient.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.
The text was updated successfully, but these errors were encountered: