Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
setycz
3 years agoExplorer | Level 3
Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: E
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?
15 Replies
Replies have been turned off for this discussion
- Greg-DB3 years ago
Dropbox Community Moderator
I've tried your sample code and the issue doesn't reproduce for me, so it may be specific to some aspect of your environment or account.
That being the case, to help us track down these specific failures, please open an API ticket here and share the following:
- Have you made any modifications to the Dropbox SDK? If so, please share them.
- Please include several 'X-Dropbox-Request-Id' response header values for several responses with the error shown here.
- Please include the IP address used to make the requests that resulted in the errors identified in the previous item.
Thanks in advance and apologies for the bother!
- setycz3 years agoExplorer | Level 3
Hello Greg-DB,
I have reproduced the issue today and submitted the request as you suggested. It was actually pretty hard to reproduce it today, it took 1432 requests. I'll also post the data you asked for here:
- Have you made any modifications to the Dropbox SDK? If so, please share them.
- no changes
- Please include several 'X-Dropbox-Request-Id' response header values for several responses with the error shown here.
- [X-Dropbox-Request-Id]=[5540b28dca5e40c1aa5ecde595c983a5]
- Please include the IP address used to make the requests that resulted in the errors identified in the previous item.
- (I won't rather post it here, but it is included in the ticket :D)
Thank you for your help.
- Have you made any modifications to the Dropbox SDK? If so, please share them.
- Greg-DB3 years ago
Dropbox Community Moderator
Thanks for submitting that. The team will review your ticket and follow up with you there.
- STEALTHbits3 years agoExplorer | Level 4
Greg-DB setycz I am wondering if something was fixed, I was seeing this error back in late June/early July and handled the exception itself. However, as of July 21st I have not seen it. For me this error was occurring after an hour runtime of consistent calls to GetSharedFile/FolderMembers
- Greg-DB3 years ago
Dropbox Community Moderator
STEALTHbits Yes, the team worked on tracking this down and resolving it.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
The Dropbox Community team is active from Monday to Friday. We try to respond to you as soon as we can, usually within 2 hours.
If you need more help you can view your support options (expected response time for an email or ticket is 24 hours), or contact us on X, Facebook or Instagram.
For more info on available support options for your Dropbox plan, see this article.
If you found the answer to your question in this Community thread, please 'like' the post to say thanks and to let us know it was useful!