Closed anne-a closed 5 years ago
@tylerlong can u look into this
Yes. I am aware of this issue and I am working on the fix.
Root cause: https://github.com/dotnet/corefx/issues/1794#issuecomment-333193361
So .net core doesn't auto dispose it while .net framework does. So this is a .net framework only issue.
Released version 2.0.2
For certain error cases, we're getting the error - 'Cannot access a disposed object' instead of the real error message. For example, when trying to authorize with the code below:
If there is a problem with the credentials, e.g. an incorrect password, the SDK throws the following exception:
Similarly, when trying to make a call using Call Sessions (code sample below), if any of the input parameters are invalid (device ID or phone number), we get the same exception thrown - 'Cannot access a disposed object'
This exception being thrown is preventing us from being able to display a meaningful error to the user. Would it be possible to get a more specific error returned?