Greg-DB Dropbox Community Moderator

Can you share the steps and code to reproduce the issue? Thanks in advance!

No, I don't have a timeline to share.

That feature is in the process of being rolled out, so it will be set for some users and not others. The field is marked optional, so make sure your app doesn't rely on it being set.

It sounds like you're referring to the response from /2/sharing/get_file_metadata. That endpoint is released and is not in preview/beta, so you can use it in production. The SharedFileMetadata.preview_url is documented as "URL for displaying a web preview of the shared file." The SharedFileMetadata.link_metadata.url is…

https://api.dropboxapi.com/oauth2/token is the correct URL. You can find the current documentation here: https://www.dropbox.com/developers/documentation/http/documentation#oauth2-token

That's correct, folders are not considered to have revisions. File revisions are stored for 30 days by default, or longer depending on the account type/features: https://www.dropbox.com/help/space/older-versions

[Cross-linking for reference: https://stackoverflow.com/questions/45430985/adding-dropbox-credential-hardcoded-in-android-instead-of-asking-the-client ] The API was designed with the intention that each user would link their own Dropbox account, in order to interact with their own files. It is technically possible to…

Dropbox doesn't offer any sort of API for querying the status like this unfortunately. I'll send it along as a feature request.

Thanks! That is the response we're looking for. The /2/files/get_temporary_link documentation covers what the 'not_found' error means. In this case, it does mean there was nothing found at the path supplied in the 'path' parameter. How are you checking that the folder does contain 1.dcm and 2.dcm? Be careful checking via a…

Thanks! That "HTTP/1.1 409 Conflict" is part of the API response, but it's only the status line. Can you print out the rest? The response body should contain a specific error.

Does this happen on every attempt, or only occasionally? Can you share the full error output?

Thanks! By the way, it looks like you're not using the official Dropbox API v2 Java SDK. We do highly reccomend using it, if possible. In any case, whether or not you're using it, it does just look like this error is due to intermittent DNS issues, so you should look into why your DNS queries may be failing occasionally.

No, unfortunately there isn't an interface or notification system provided for this. I've sent this along as a feature request.

Using instanceof is the right way to check the type of a Metadata object, as shown in this example. Note that FileMetadata, DeletedMetadata, and FolderMetadata are mutually exclusive though. That is, any given Metadata object can only be one of those three subclasses, but not two of the three. For example,…

Based on your other thread, it sounds like you're only using the Chooser/Saver, so you don't actually need to apply for production. (For future reference though, if you were using the Dropbox API itself, you could request a review before you have linked users by requesting an "early review". There's more information about…

First, you would enable additional users for your app via the App Console. It sounds like already did that, based on the "0/500" figure you shared. Then, you would distribute your app to your testers to link to your app normally, as if the app was already released for real. Based on your description of "they have…

This error message indicates an issue with the third party app's configuration. The developer of the third party app will need to correct the configuration of their app to fix this. You may want to reach out to them to ask them to fix it.

[Cross-linking for reference: https://stackoverflow.com/questions/45397501/dropbox-does-not-auto-rename-file-during-upload ]

There's no accumulating penalty. The additional calls will just receive the 429 response with the Retry-After value. The Retry-After value is generally not more than a few minutes. (I believe the Retry-After value may effectively get reset with each rate limited call within the rate limiting window, but if they're all…

I'm glad to hear you sorted that out already. For reference though, it looks like you're using a third party SDK. As it's made by a third party, we wouldn't be able to provide support for it. Also, it unfortunately looks like that SDK uses the old Dropbox API v1, which is deprecated, and going to be retired soon. You…

Thanks! That's helpful. So, the "Invalid URL" error isn't coming from the API itself, but rather just from this line of code: if ($response === false) { $response = "Invalid URL: ".$url;/*echo "Problem reading data from $url.";*/ } That will occur if `$response` is false, and `$response` will be false based on…

@"TejaVarma" It looks like you didn't post the entirety of the issue. Can you share the code and full output that's giving you trouble? Based on what you did post though, it looks like you're getting a UnknownHostException for api.dropboxapi.com. Per the documentation for java.net.UnknownHostException this error indicates:…

Calling listFolder with "" to identify root, with recursive=true, and calling back to listFolderContinue as necessary like this is the correct way to list all of the files.

The Dropbox API does have a rate limiting system, but we don't have any specific numbers documented. Also note that not all 429s and 503s indicate rate limiting, but in any case that you get a 429 or 503 the best practice is to retry the request, respecting the Retry-After header if given in the response, or using an…

@"ravisharma" What are you looking for exactly? If you need to see how to distinguish between files and folders, that's in the README: https://github.com/dropbox/SwiftyDropbox#response-handling-edge-cases If you're looking for a sample for listing items, there are some examples here:…

It looks like your client object is probably going out of scope before the request can finish. Note that the actual API calls are made asynchronously, so the client object may be gone by the time the network call finishes. Try keeping your client around instead. For example, you can use…

Yes, it sounds like you're referring to using the OAuth 2 "code" flow, without providing a "redirect_uri". You can find more information on that in the documentation here: https://www.dropbox.com/developers/documentation/http/documentation#oauth2-authorize

The API doesn't offer a way to query the sync folder path, but I'll pass this along as a feature request. If your app is running on the machine though, you can find it using the info.json file documented here: https://www.dropbox.com/help/desktop-web/find-folder-paths

Thanks Bryan. That is the correct URL for this API endpoint, and that doesn't seem to be the actual API request/response though. For example, using curl, this works for me: (just using a made up 1.dcm file in my test account) $ curl -vX POST https://api.dropboxapi.com/2/files/get_temporary_link \ > --header "Authorization:…

Hi Bryan, to clarify, are you calling /2/files/get_temporary_link with that parameter? That shouldn't produce an error like that. Please share the full request and response (just be sure to redact the access token) so we can take a look. Thanks!