Child Item

Failed to Load Request Error when using Chooser API

We use the Dropbox Chooser API and have recently started having a problem with it . Now when the user selects a file from the Chooser pop-up then clicks "Choose" to confirm their selection, an error appears saying "Failed to load request". The pop-up window does not close and nothing is returned to our app.

Nothing about our code has changed in a long time that I'm aware of. I have confirmed that our app has the appropriate permissions in the App Console, and our API key is correct. Was there something that changed on Dropbox's end that would cause this to start happening? It happens in all browsers we've tried it in (Chrome, Edge, and Safari on Windows 10, macOS, and iOS)

Find more posts tagged with

Comments

DB-Des

Hi @Harsimranjeet007

We'll be happy to help with any issues you're having, but we'll need some more information. Please reply with:

the steps to reproduce the issue, including relevant code snippet(s), but don't include any access or refresh token(s)
the full text of any error or unexpected output
screen recording of the issue with the developer console open

Harsimranjeet007

Hi..

We are intergrating the dropbox chooser feature in our cloud storage application (currently this new feature is in testing phase). When the chooser popup appears (after the user has provided his dropbox credentials) and user clicks on choose option after selecting a file then we are getting "Failed to load request" error message inside the dropbox chooser popup. Please refer the below screenshots.

Response of the share api call made at https://www.dropbox.com/dropins/share ::

<!DOCTYPE html>

<html>

<title>Dropbox - 400</title>

</head>

<body>

</div>

<h1>Error (400)</h1>Something went wrong. Don't worry, your files are still safe and the Dropbox team has been notified. Check out our <a href="https://status.dropbox.com">Status Page</a> to see if there is a known incident, our <a href="https://www.dropbox.com/help">Help Center</a> and <a href="https://forums.dropbox.com">forums</a> for help, or head back to <a href="https://www.dropbox.com/home">home</a>.

</div>

</body>

</html>

DB-Des

@Harsimranjeet007

Thanks for that additional information. I am not able to reproduce the issue on my end. Could you confirm whether this issue is persistent across different users as well?

Also, do you have a sample page that reproduces this issue that you can share? Otherwise, can you share the specific code/parameters you're using to set up the Chooser on your app so we can reproduce this? Feel free to open a ticket here if you'd prefer to share privately.

Harsimranjeet007

Hi..

This issue is happening for newly created dropbox accounts. I tried this workflow for my old dropbox accounts it worked fine but failed to work for newly created dropbox accounts.

I am sharing a snippet of a code that we are using to launch the Dropbox chooser

DB-Des

@Harsimranjeet007

Apologies for the delayed response here.

I see that you’ve since opened a support ticket, so we’ll continue the conversation and follow up with you directly there to make sure this gets addressed.

aaliyamalikk

Nothing about nekopoi code has changed in a long time that I'm aware of. I have confirmed that our app has the appropriate permissions in the App Console, and our API key is correct. Was there something that changed on Dropbox's end that would cause this to start happening? It happens in all browsers we've tried it in (Chrome, Edge, and Safari on Windows 10, macOS, and iOS)

DB-Des

@aaliyamalikk

Thanks for checking in.

There haven’t been any recent changes on our side that would cause the Dropbox Chooser to stop working, and we haven’t received reports from other customers seeing similar behavior. We’re also not able to reproduce the issue on our end.

To help us investigate further, do you have a sample page that reproduces this issue that you can share? Could you also share a screen recording of the flow you are following when the issue is encountered? From beginning to end, with the developer console open. Please ensure that the whole browser window can be seen as well.

A HAR file might be helpful also.