Greg-DB Dropbox Community Moderator

@"redm" Thanks for the report! I see your support ticket was received. We'll look into it.

I'm afraid there isn't a way to speed up these calls unfortunately, but I'll pass this along as a feature request. I can't promise if or when that might be improved on though. 

I'm glad to hear that works well. The chunk size is how much data to read from the Dropbox API and then write to the local file at a time. I used 4 MB in this sample, but you can change that as desired, with the constraint being how much memory you can use. I'm not sure why that link got broken again, but I fixed it again…

Apologies, I had the wrong link in that post. I just fixed it. It should be this post. Anyway, it looks like the issue is that you're running out of memory when downloading the file, since you're accessing the whole thing, and the file is very large. You can read off the download result in pieces like this: with…

In Python, a MemoryError is "Raised when an operation runs out of memory". That certainly seems possible here given the file sizes you mentioned. This new line of code seems to reference several things not included in the original code you shared, and doesn't seem to mention Dropbox. Is this new code of yours, or is it…

@"Dennyw" I'm afraid I don't have an update on this. The request has been shared with the team, but it looks like there still aren't plans for work on this.

It looks like you may be silently dropping exceptions, based on this code: except: continue Add some error handling there to see what may be going wrong with writing the file. At least something like: except Exception as e: print(e) continue

Dropbox API v2 parameter names are case-sensitive. The parameter you're trying to use on /2/files/list_folder is named "path", so you'll need to specify "path" instead of "Path".

@"Traye1" I've redacted it from your post, but for future reference, please do not post or share your access token, for your security. Anyway, the specific request IDs would be ideal, but I'll try to look this up without them. I'll let you know when I have an update on this.

Thanks for the report! We're aware of this issue and are looking into how to solve it. (We may offer a new method for cleaning up the Embedder after unmounting, or possibly handle this automatically, if possible.) I'll follow up here once I have an update on this.

Yes, using /2/files/list_folder[/continue] is the right way to list the files in an account. To list every file, you would set the 'path' parameter to the empty string "" (not "/"), and set 'recursive' to true. The error you're getting indicates that the call failed because the HTTPS request body was empty, instead of…

Thanks for the additional information! I still can't say off hand exactly what the issue may be, so I recommend starting with the posts linked in my previous comment.

@"Shanness" I still don't have an official update on this unfortunately. (For reference, it looks like this can occur due to some implementation details on the backend of how account migrations work with respect to Paper docs. That is, during the migration some extraneous doc IDs may be left over, but these don't actually…

The /2/file_requests/list_v2 endpoint is for listing 'file requests', not actual files. (A "file request" is a way to receive files from other people.) To list files, you should instead use /2/files/list_folder[/continue].

A 'path/conflict/folder' error like this indicates that the upload failed because there is already a folder at the specified path (not a file). The "overwrite" mode will only overwrite files, not folders. When uploading a file, e.g., using files_upload, you need to specify the whole path where you want to put the uploaded…

Are you using the same version of Visual Studio and same project in both the developer machine and virtual machine? Given that this only happens inside the virtual machine, it sounds like there's an issue with the development environment in that virtual machine, in which case we may not be able to offer much support, as…

Thanks for the information. It sounds like something during the processing of removing the member is taking a long time on the Dropbox server, and eventually timing out server-side. Would you be able to share the response headers though? In particular, a few sample 'X-Dropbox-Request-Id' values would be helpful in tracking…

Dropbox does offer an API you can use for listing, uploading, and downloading files, among other operations. You can find everything you need to get started with the Dropbox API, including documentation, tutorials, and SDKs here: https://www.dropbox.com/developers For example, to upload files, you can use /2/files/upload:…

File events are not available for all Dropbox Business plans. Please refer to the /2/team_log/get_events description for more information on this.

Dropbox does not currently offer an API for managing comments. When adding a member to a folder, you can only set their access level to either AccessLevel.Editor.Instance or AccessLevel.Viewer.Instance. AccessLevel.ViewerNoComment.Instance is not currently supported for that. 

@"Sekali" I'm not sure I understand your message. If you're using an official SDK, such as the Java SDK, you should use the latest version, as released and documented. You do not need to make any modifications to it. It may use some different internal mechanisms, but the latest versions already use API v2. If you are not…

Engineering let me know they're looking into it, but unfortunately we don't have a timeline for a fix right now. That being the case, you may want to use files_search_v2/files_search_continue_v2 as a workaround for now. 

This is currently open with engineering, but I don't have an update on it yet. I'll follow up here once I do.

@"guymayor" Thanks for checking in. We were able to reproduce this issue internally. This is now open with engineering, but I don't have an update on it yet. I'll follow up here once I do.

Thanks for following up. I'm glad to hear this is working for you again. The Dropbox API wouldn't block access like this. If the Dropbox API rejects a call, it returns an explicit error message, not a network block. It sound like there was a networking issue preventing your server from reaching the Dropbox API servers.…

Dropbox does offer an API you can use for listing, uploading, downloading, and sharing files, among other operations. You can find everything you need to get started with the Dropbox API, including documentation, tutorials, and SDKs here: https://www.dropbox.com/developers For example, it sounds like you may be interested…

The /2/files/list_folder endpoint only supports "user authentication", meaning it does require an access token. It does not support calling just using an app key/secret. It sounds like you're probably using an access token retrieved via the API Explorer though. The API Explorer has early access to an upcoming feature where…

Dropbox has an abuse detection system in place to detect and prevent automated logins to help protect our users. It uses a variety of factors to decide whether or not to display a CAPTCHA or verification challenge like this, so whether or not you see it, or exactly what you see, may vary over time. Dropbox doesn't provide…

@"samoaste" Thanks for the feedback! I'll send this along.

The Dropbox API does not offer a way to get an access token just by exchanging the app key and secret. The app key and secret only identify your app itself. In order to access a Dropbox account, the app needs authorization from the account owner. Typically, to get authorization from the user and receive an access token for…