We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
It must exactly match one of the redirect URIs you've pre-configured for your app (including the pat
I'm completely confused. I do it according to the documentation, if I make a link with my hands in my browser and insert the AppiKey, then everything works, if I try to do it through the code, ...
Shy1 wrote:i am just delete anchor and error disapear. ...
Shy1, Hmm.. 🤔 How have you deleted something nonexistent? I can see some anchor in your code responsible for redirect URI construction! I'm not sure you have some "configuration pc problem", but most probably you are mixing anchor and resource path. 🙂
Shy1 wrote:... but at the browser url i have request
Probably you mean the "redirect_uri" parameter there. Is the parameter value registered in the form it appears without your "correction"? 😉
Let me guess what's there. At the beginning you have a constant:
private const string LoopbackHost = "http://127.0.0.1:4200/";
The 'LoopbackHost's value is clear, as you noted it's "http://127.0.0.1:4200/". Let's see the next value:
// You also need to register this redirect URL on https://www.dropbox.com/developers/apps.
private readonly Uri RedirectUri = new Uri(LoopbackHost + "authorize");Now we have previous value concatenated with "authorize" (i.e. 'RedirectUri's value is "http://127.0.0.1:4200/authorize"). 😉 Is that what appear? And as noted (in the comment), had you registered it? 🧐
About how your PC handle it, take a look here:
while (context.Request.Url.AbsolutePath != RedirectUri.AbsolutePath)
You code waits for the same 'RedirectUri's value and ignore everything else (keeps looping) until appearing. Can this even happen in your case? (your PC receives this value "corrected" by your hand!!!)
yes, I have it registered, because I can read. I get a response from the correct link, but my bowser gets the following error and the code exits without any exceptions, it just dies out. if I go through the debugger then I get to the HandleJSRedirect and everything ends there and if not through the debugger, then it ends on the process call Process.Start(); I do not understand anything
ERR_CONNECTION_REFUSED link what i have but i cant work with her and link down
maybe it's how i run it?
static void Main(string[] args)
{
Program program = new Program();
var task = Task.Run(program.MainRun);
task.Wait();
}
public async void MainRun()
{
var accessToken = await this.GetAccessToken();
}
Shy2 wrote:... if I go through the debugger then I get to the HandleJSRedirect and everything ends there ...
On the previous call (call to 'HandleOAuth2Redirect') you have to send back to the browser a 'index.html' file (actually almost entire javascript content), responsible for additional redirection that seems missing. Are you sure correct content got the way? 🧐 You usually can debug/check this using the embedded browser tools (trace the communication). After the second redirect your browser should get redirected to something like:
http://127.0.0.1:4200/token?url_with_fragment=...Does this happen?
if I take an example from github, and just change the AppKey and AppSecret and set my port, then everything goes fine and I get the following error: an error occurred while sending the request at the moment Exchanging code for token
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
