Greg-DB Dropbox Community Moderator

Yes, that update was deployed towards the end of January.

Thanks for following up. I'm glad to hear you got this working. I can't provide guidance on what other headers you should or shouldn't be setting though, as that depends on how the app works and what the app does.

That's correct, the ListMountableFoldersAsync method in the .NET SDK returns a ListFoldersResult with Entries being a list of SharedFolderMetadata. There's a SharedFolderMetadata.Name property that you can use to get the shared folder name.

Thanks for the additional information. So, it looks like the "corrupted" download has an extra 13 bytes of data, which some zip utilities tolerate and which some don't. Based on this, it looks like this is because your client isn't properly decoding the HTTP message. We recently updated the server back-end for these links…

Dropbox doesn't offer a pre-built component like that for deleting files, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. You could use the Dropbox Chooser to have the user select file(s) though, at which point the app would then receive the corresponding file…

Thanks! I'll pass this along as a feature request, though I can't promise if or when that might be implemented.

We can help transfer API app ownership. Open a ticket here from the account that currently owns the app to get that started: https://www.dropbox.com/developers/contact

Can you try inspecting the corrupt download to see what the issue is specifically? For example, compare it to the original file to see why it does not appear to be a valid zip file. Also, note that curl's "-I" doesn't actually download the file, so that may not be a useful test. Here's how you should actually do this with…

With the API v2 JavaScript SDK, you can make a copy of a file using the filesCopyV2 method.

That's correct, you can't add members to non-shared folders. The folder will need to be shared (e.g., via /2/sharing/share_folder) so that it will have a shared folder ID before you can add members.

Apologies for the confusion. It looks like that was supposed to be "Dropbox-API-Select-User" instead. Please try that out and let me know if that doesn't work for your use case.

Can you clarify what you mean when you say the file is corrupted? What is in the downloaded file? For example, is it empty, or missing data, longer than expected, etc? Also, note that the "-I" option on curl only performs a HEAD request, meaning it only requests the headers, so it won't return the actual file data to…

There isn't another link type that I can refer you to that won't necessarily use this transfer encoding. "Transfer-Encoding: chunked" is part of the HTTP spec so I can't guarantee it won't be used for any particular URL. You should update your client to support this, and/or HTTP/2.

No, we don't have specific documentation on this for the Dropbox API, but I'll pass this along as a request. I can't promise if or when that might be added though.

I'm not aware of any reason off hand that .m4a should works but .ogg wouldn't. Note that using Postman may not be representative of your actual video player client on Android though, as they may use different HTTP versions or features. Are you able to get any logging output for the actual client on Android?

I understand you're programmatically accessing Dropbox shared links, and have been relying on the "Content-Length" header being set on responses. Please note that Dropbox does not guarantee that the "Content-Length" HTTP response header will always be present on the responses for these URLs though. For example, when the…

Dropbox still doesn't support wildcards in OAuth 2 redirect URIs. One workaround to this is to instead use one static redirect URI (say, on a particular non-changing domain you control), but encode the necessary information (such as the changing domain) in the 'state' parameter, and decode it as necessary after the…

Thanks, in that case if the 500 isn't coming from Dropbox itself, this may be because we recently updated the server back-end for these links to use "Transfer-Encoding: chunked" (and accordingly not return the "Content-Length" response header) on HTTP/1.1. HTTP clients should automatically handle this, but it's possible…

@"Aristide" Здравко is correct, this error is referring to the sharing permissions for the particular file/account, not the app scopes. For reference, an 'access_error/no_permission' from /2/sharing/add_file_member means: access_error SharingFileAccessError (open union) no_permission Void Current user does not have…

No, the cursors returned by the search endpoints are meant for pagination and do not promise to track changes over time. Also, the search endpoints require some query, so they don't support just searching for all files of a particular file type anyway, but I'll pass this along as a feature request. I can't promise if or…

Short-lived access tokens expire after a few hours (be sure to check the actual API response for the specific expiration time). If the app requests "offline" access and stores the resulting access token, it does not need to send the user through the app authorization flow again, as it can use the refresh token without…

Whenever you use SaveUrlAsync, you should also implement support for calling SaveUrlCheckJobStatusAsync, as you aren't guaranteed to get the completed result immediately on SaveUrlAsync. The SaveUrlResult from SaveUrlAsync can be either the complete result (IsComplete), or an async job ID (IsAsyncJobId). If you get back a…

Are you able to retrieve any specific error message or output? We did recently update these links to use "Transfer-Encoding: chunked" (and accordingly not return the "Content-Length" header) on HTTP/1.1, but HTTP clients should automatically handle this. It's possible yours doesn't, however. Also, that change was rolled…

@"burgerman" I don't have any news on this unfortunately.

If you haven't already, you may want to start with the Getting Started guide here: * https://www.dropbox.com/developers/reference/getting-started And for information on how to have the user authorize your app so the app can access their account, check out the OAuth Guide and authorization documentation: *…

I just have to save a refresh token locally and generate a new access token with an api request when the expiration has arrived? Yes, that's correct. To maintain long-term access, you should store and re-use the refresh token whenever needed. You can get a new short-lived access token whenever needed by calling…

Can you clarify where exactly you're seeing the 500 error? Is that coming from the Dropbox servers, or some other part of the process? It would be helpful if you can show the error/output in context. Thanks!

As you found, Dropbox is currently in the process of switching to only issuing short-lived access tokens (and optional refresh tokens) instead of long-lived access tokens. You can find more information on this migration here. Apps can still get long-term access by requesting "offline" access though, in which case the app…

No, these shared links (whether from create_shared_link_with_settings or sharing_create_shared_link) are per-user. Each such shared link is owned by a specific user account and the API doesn't offer a way to change that.

There isn't a particular maximum download size recommendation in this case. (The upload request limit you mentioned is due to a particular server-side limit with respect to reliability, which doesn't apply to downloads.) So, this would be up to you, likely mainly as a matter of how much memory on the device you're willing…