Dear support,
since 20th May we have started to encounter random failures when invoking `DropboxClient.Files.ListFolderAsync` function, see the following stacktrace:
Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: E. Path '', line 0, position 0.
at Newtonsoft.Json.JsonTextReader.ParseValue()
at Dropbox.Api.Stone.JsonReader.Read[T](String json, IDecoder`1 decoder)
at Dropbox.Api.DropboxRequestHandler.<RequestJsonString>d__20.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Dropbox.Api.DropboxRequestHandler.<RequestJsonStringWithRetry>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Dropbox.Api.DropboxRequestHandler.<Dropbox-Api-Stone-ITransport-SendRpcRequestAsync>d__12`3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
One day the same code with the same storage works and the other it does not. This and the fact that the JSON response from DropBox seems to be invalid indicates that the issue might be with DropBox API it-self. The issue seems to be appearing more often lately.
Our application is .NET Framework 4.8 and using Dropbox.Api 6.30.0.
Were there any recent breaking changes? Could you check the API on your side? Or recommend any actions we can take?