More context might help understand what was going on and whether a retry did what was needed.
Increasing logging level from Warning to Retry should do that. As for the line 0, positon 0
, I’ve wondered (along with others) if the network did something odd (like close its connection on you…), however capturing data at that level is technically difficult, especially if the error is very intermittent.
Dropbox: Error reading JObject from JsonReader. Path ”, line 0, position 0 was a case on Dropbox.
If you go for network tracing, note the warning about how you’re capturing unencrypted information.
Encrypted information can be obtained from Wireshark, but would take even more guessing over it.
Easiest and OK result would be to find that whatever upload/download/list/etc. worked OK on retry.