nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Child Item

.Net v2 SDK DropboxOAuth2Helper.ProcessCodeFlowAsync

Ivan_Gusev

Hello!

We use the Official Dropbox .Net v2 SDK

Some of my clients are getting this message if they try to enter confirm oauth code.
We have checked their detailed debug log and we have noticed, when the app invokes
DropboxOAuth2Helper.ProcessCodeFlowAsync
then it returned the error:
Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: <. Path '', line 0, position 0.
But, it looks like there is no way to get a full response message from the dropbox server with a detailed information related to this error.
I'm wondering, is there any way to get a full response from the service in this case?

In fact, we have many installations of our application and this code working fine on many of them, but there are a few installations with this strange error message.

Find more posts tagged with

API

Abuse

Comments

Greg-DB

It looks like you should be able to configure network tracing as shown here for additional output:

https://docs.microsoft.com/en-us/dotnet/framework/network-programming/how-to-configure-network-tracing

Is there any particular input (for the 'code' parameter) that is causing this though? We can try to reproduce this here if we know the steps to do so. Thanks in advance!

Ivan_Gusev

Hello Greg,

We can not reproduce the issue like our client gets, also we do not know what "code" he had.

You can get a similar, but not quite the same, error message if you enter "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa" instead of the authorization code.

In the network.log, I can see the following message "Internal Server Error".

But the client seems to get another response, in which he has the first character "<".

We will ask the client to enable network.log

Greg-DB

Thanks! The "Internal Server Error" for a malformed code like that is a known issue.

Please do let us know if you get the log for the "<" issue though. That may be a different issue, so we'll need to figure out how to reproduce it. I suspect there's some unexpected value being sent that is causing the call to fail like that. Thanks!