Your workflow is unique 👨💻 - tell us how you use Dropbox here.
Forum Discussion
Standa Fy
1 year agoExplorer | Level 4
Embedder fails to load
Hi, I am using the embedder in Angular application and unreliably(and with no clear pattern I can see) it fails to load data. I can see that the iframe is created in the element after the embed func...
DB-Des
Dropbox Community Moderator
1 year agoHi Standa Fy,
Could you also confirm that you have added the respective domain(s) for the app you are using in the app's "Chooser / Saver / Embedder domains" field, from within the App Console?
DB-Des
Dropbox Community Moderator
1 year agoHi Standa Fy,
Just wanted to provide you with an update.
After thorough testing, we were able to replicate the issue have described. However, it appears that the problem is isolated to the Chrome browser.
During our tests, we found that the issue could not be reproduced in other browsers, such as Safari and Firefox, where everything functioned as expected. This suggests that the issue is likely specific to Chrome.
- Standa Fy1 year agoExplorer | Level 4
Hi DB-Des,
yes the domains are added and the functionality works as expected save for the random occurrences of the problem described.
Yes as I wrote the problem manifested for me only in Google Chrome which is however largest by marketshare. Now that you have confirmed the issue what have you decided will be the resolution, if any? - Greg-DB1 year ago
Dropbox Community Moderator
Standa Fy Thanks for providing the sample. I also tried this out and was able to reproduce the issue with your sample in Chrome. When inspecting the relevant request in the developer tools in Chrome, I see the request does receive a response, including a successful status code (200) and headers. When attempting to view the response body, Chrome instead shows an error "Failed to load response data: Request with the provided ID does not exists", which seems unexpected, since the request does exist (as Chrome is already showing the relevant request information).
From what we've found so far, there doesn't seem to be a failure on the Dropbox side, so I'm afraid there isn't anything we can fix for this on our side. It appears to be an issue in Chrome around the request/response handling in this sort of scenario.
About Dropbox API Support and Feedback
Get help with the Dropbox API from fellow developers and experts.
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!