Greg-DB Dropbox Community Moderator

Unfortunately, the Dropbox .NET SDK doesn't currently officially support C++, but I'll be sure to pass this along as a feature request. 

Rich is correct, shared links only point to an HTML preview page by default. If that's the issue, you'll need to modify them as he described. There's a help article that documents these options here: https://www.dropbox.com/help/201

Hi Tiago, if I understand your question correctly, no, API v1 and API v2 aren't compatible interfaces. That is, while API v2 has almost all of the functionality of API v1, the way API v2 calls are made, the parameters, and the data structures are different, so you can't just drop in the new respective endpoints in the same…

No, in that case they would have distinct IDs.

Apologies we don't have better documentation on this right now! I'll send this along as a request for some. To answer your actual question though, there are a few things to note: - file IDs are not content hashes. That is, files with the same exact content in two unrelated accounts will have different IDs. - a single…

The equivalent of v1's getDelta (without a cursor) is listFolder, and the equivalent of getDelta (with a cursor) is listFolderContinue. Likewise, the equivalent of getDeltaLatestCursor is listFolderGetLatestCursor. If you want the full state of the files in the account, you should start with listFolder (as opposed to…

Hi Timm, Richard's correct, the Dropbox API doesn't exactly have a concept of a sync being "done". When the Dropbox servers receive a change, (e.g., a single file upload via a single API call) it just sends off a webhook notification to let you know about it. Dropbox doesn't know if there are further changes coming, so it…

Hi Billy, a Metadata object like in your sample can be for either a file, folder, or deleted object, so you need cast it to the respective type, FileMetadata, FolderMetadata, DeletedMetadata, to access the properties specific to each. For example, you can do something like this: System.out.println(metadata.getPathLower());…

Hi Artem, I can't seem to reproduce this issue with Firefox 47 or IE 11. Also, the Dropbox API server certificates aren't revoked to my knowledge. Might there be something on your network connection intermittently interfering with your connections to the Dropbox API servers? E.g., firewall, proxy, anti-virus, etc.?

Unfortunately I don't believe we have explicit support/instructions for using the Java SDK with ******/GWT, but I'll be sure to pass this along as a request.

I see, thank you for the additional information and screenshots! I'm including it in the report with the team.

Thanks for the additional information Olive, that's helpful. Based on your original screenshot too, it looks like you were always getting the desktop version of this page, but this issue just arose due to some styling changes. I'm reporting this to the team, but I can't make any promises for a fix right now. If you have a…

Do you know what the User-Agent for your UIWebView is? It looks like you're actually getting the desktop version of this page (which isn't fitting in that narrow UIWebView).

Apologies for not following up on this thread, Olive! This should already be fixed. Are you still seeing this? (This may work differently in your app of course since you're not using the SDK, so if you are still seeing an issue, please supply a screenshot showing the current state of the page in your app.)

Thanks for writing this up Olive! The formatting on this page is a known issue we'll fix on our side.

1) The /save_url endpoint only supports individual files, but you can call it repeatedly to save multiple files. Also, any parent folders that don't exist in the paths you specify will automatically get created. 2) You can make API calls to whatever accounts you have access tokens for.

You need to URI escape your parameters. In your sample, you're not escaping the whitespace in the destination, which is breaking up the pieces you're giving to curl, corrupting the command. That is, curl thinks you mean "PM" is another host you want to connect to. Your curl command should probably look something like: curl…

The /1/save_url endpoint doesn't support the GET method, so you should use the POST method to call this endpoint. Exactly how you change what method you're using will depend on your HTTP client. For example, with curl on the command line you would supply the option "-X POST".

Yes, the Dropbox API does offer the ability to get shared links for files. If you use the Python SDK, you can use the sharing_create_shared_link_with_settings method. Or, if you prefer to use the HTTP endpoints themselves, that's /2/sharing/create_shared_link_with_settings.

The order isn't guaranteed by /list_folder, so either way can occur. The guarantee is just that you'll get a correct representation of the state if your app processes all of the entries in the order given. Your app can then apply whatever sorting it wants once it has the entries.

If I recall correctly, I believe you should get multiple pages after around 1,000 items. There isn't a way to force the limit though.

We don't guarantee any particular page size, and I believe it can vary in practice. Apps should always just check has_more and call back to /files/list_folder/continue if it's true, and so on.

The API was designed with the intention that each user would link their own Dropbox account, in order to interact with their own files. However, it is technically possible to connect to just one account. The SDKs don't offer explicit support for it and we don't recommend doing so, for various technical and security…

Hi David, here's an example of using files.download with every error case handled in Swift: (apologies for the poor formatting on the forum) Dropbox.authorizedClient!.files.download(path: path, destination: destination).response { response, error in if let (metadata, url) = response { print("*** Download file ***")…

Specifically, I mean are you getting anything else from your app (e.g., other output or errors) that leads you to believe that's the case beyond that warning log message though? I believe that warning just indicates that a freed connection wasn't being returned to the pool because the pool is already full, not that any…

Can you elaborate on what you mean when you say you "believe these connections are being dropped, so some of the work is not executed when it should be"? Is there any error or output you can share?

The connection pooling should be handled for you. Are you getting failed requests when you see this warning logged? If you'd like, you can control the max_connections by creating a session: https://dropbox-sdk-python.readthedocs.io/en/master/moduledoc.html#dropbox.dropbox.create_session and then passing that in when…

There isn't a great way to test this from your side ahead of time, since the actual change will just be a change in the certificate being used on the Dropbox API servers. As long as the upgrade (either SDK or just certificate file) works when you do the upgrade, we don't expect any issues when the new certificate is in…

1. Yes, your API calls will fail once the Dropbox certificates are changed to ones not covered by the certificate file included in your copy of the SDK 2. We recommend upgrading the SDK entirely, and we'll be happy to help with any issues you have while doing so. Looking at the CHANGELOG.md file, I don't see any breaking…

Hi Artem, as you saw in the API Explorer, for these calls with the parameters in the header, you need to escape these characters. That is, when you use the “Dropbox-API-Arg” header, you need to make it “HTTP header safe”. This means using JSON-style “\uXXXX” escape codes for the character 0x7F and all non-ASCII characters.…