Greg-DB Dropbox Community Moderator

@"miago" The 'BadRequestException' seems to indicate you're getting a 400 error from the Dropbox API. Are you able to print out the response body itself? It generally should contain a more useful error message. Or, please let me know if the response body is actually empty. Thanks!

Can you print out the response body itself? It generally should contain a more useful error message. I'm not sure if that's what the 'error: ""' part would already be printing so please let me know if you are actually just getting an empty response body. Thanks in advance! 

Thanks for the report! We're looking into it. Have you been trying this with a "Get Started with Dropbox.pdf" file? It looks like there's a configuration issue with that file that is preventing it from being selected in the Chooser, but let me know if you're also seeing this with other files. Thanks!

Thanks, that's helpful. That confirms you're getting one identical entry per page, and a different cursor for each page. This doesn't reproduce for me, so we'll need to investigate further on the server-side to find out why this is happening for you. I'll follow up here once I have an update for you.

@"TobiasR" Thanks! This thread is a good place for feedback like this. It looks like we already have this issue fixed internally, so that fix should be rolling out soon, likely within a day or two.

Thanks for the report! We'll look into it. We may need to add some sort of cleanup method for this kind of use case. I'll follow up here once I have an update for you.

Thanks for the report! It looks like the SDK is receiving invalid JSON for some reason. I'm not aware of anything that should be causing that right now, and I can't seem to reproduce this myself, so we'll need to look into it specifically for you. Would you be able to print out the problematic response body? That may help…

I'm glad to hear you already sorted this out. Thanks for sharing your solution!

Thanks! Can you share the updated code with this extra logging too? That would help illustrate what exactly is producing this output. As for the number of calls being made, you don't need an actual counter; I just meant to illustrate each call to files_list_folder and files_list_folder_continue, which your logging appears…

You can store the last received cursor from /2/files/list_folder or /2/files/list_folder/continue and then call back later to /2/files/list_folder/continue with that cursor. The response will contain entries for the changes since you last called. Check out the /2/files/list_folder documentation for more information on how…

Webhooks can tell you when something changed, but not what changed. To find out what changed, you would then use the list_folder endpoints. In addition to letting you list the contents, the list_folder endpoints also enable you to keep track of new changes over time: *…

Dropbox doesn't offer a pre-built library or tutorial for a sync client, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. The Dropbox API does offer the ability to list, upload, and download files programmatically though, among other operations, so you can…

Thanks for confirming that! Also, the team is working on preventing this from happening again in the future, but they noted that they could use some more information to do so. Would you be able to share a current traceroute from a server that was affected to both of: * 162.125.8.8 * 2620:100:601b:8::a27d:808 Thank you!

There was a networking issue that prevented connections to the Dropbox API servers from some geographic areas, but that should be resolved now. Can you try again now and let me know if you're still seeing this issue? Thanks in advance! 

@"clarel" Thanks for the feedback! * It looks like this is due to one scrollbar appearing for the frame itself, and then one for the folder listing. I'll ask the team to see if we can eliminate that. * Yes, Dropbox Professional and Business customers can disable downloads via the Dropbox shared link feature. * There isn't…

Nothing looks clearly wrong in the code. Can you add some extra logging to see: * how many calls are being made to files_list_folder and files_list_folder_continue, and when? e.g., how many of that repeated folder entry do you see per call? * what the value of result.cursor is each time to make sure it is changing each…

Thanks for the report! It looks like this may just be a bug on our side. We're looking into it and I'll follow up here once I have an update on this.

No, there isn't a way to disable that button, or hide the shared link itself. Since the Embedder operates by having the page supply the shared link, the user could just inspect the page's source to find the shared link anyway, even if that button wasn't shown.

We can't provide support for Laverna itself, as that's not made by Dropbox, but we're happy to help with any issues on the Dropbox side. It sounds like you're trying to access the /oauth2/authorize page to authorize the app, and the app is supplying a parameter named "dropboxKey". That's not an expected parameter though,…

@"Mark Abrams" Thanks for the feedback! The team decided not to implement the ability to programmatically upload to file requests, but I'll pass this along and follow up here if that changes.

I'll be happy to help with any issues you're having with the Dropbox API, but I'll need some more information. Please reply with: * the name and version number of the platform and SDK/library you are using, if any * the steps to reproduce the issue, including relevant code snippet(s) * the full text of any error or…

No, Dropbox doesn't offer functionality like this anymore. While you could presumably still configure a CNAME like that, there isn't a way to get a predictable Dropbox root URL for sharing files. Every Dropbox shared link now uses a distinct URL.

That '0-SNAPSHOT' version of the dependency would be if you're building the SDK from source. That's only really necessary if you need to modify the SDK for some reason. Otherwise, I recommend just including the pre-built copy of the library as covered here. That's the first line you have commented out in yours. Do you…

Since you're attempting to use the Embedder on https://dropbox.diddo.dk/dropbox, you should register the domain 'dropbox.diddo.dk' (or just 'diddo.dk'; see my earlier comment). Do not include the protocol 'https://' since that's not part of the domain. Also, do not prepend 'www' since that's not in the actual domain…

Can you elaborate on what you mean when you say it didn't work? Specifically: * what domain did you register? * are you still testing on https://dropbox.diddo.dk/dropbox/? * what error are you getting now?

The Android example app only supports SDK 19 and up. The Dropbox library itself doesn't have a documented minimum supported Android SDK level, but I would expect it to work on any SDK level where its dependencies can work. 

It looks like you're actually using old code, from before this change in 2018 (and maybe are mixing old code with new dependencies, or vice versa?). In any case, please use the latest version of the Dropbox library, sample code, and dependencies for compatibility. The latest release of the Dropbox Java library itself is…

This can occur when attempting to use the Embedder on a domain that you haven't pre-registered for your app. (Apologies this isn't better communicated by the Embedder. I'll ask the team to see if we can improve that.) To fix this, you'll need to add your app's domain(s) to the "Chooser / Saver / Embedder domains" field on…

@"dwissing" Thanks for the note!

When using filesUploadSessionFinishBatch, "UploadSessionStartArg.close or UploadSessionAppendArg.close needs to be true for the last upload_session/start or upload_session/append_v2 call". That is to say, since filesUploadSessionFinishBatch can't itself take any further file data, you need to make sure you've already…