Greg-DB Dropbox Community Moderator

You can add a shared folder to an account via the Python SDK using the sharing_mount_folder method. You can list the shared folders available to be mounted in an account using sharing_list_mountable_folders/sharing_list_mountable_folders_continue.

You'll need to add the relevant domain to "Chooser / Saver / Embedder domains", not the "OAuth 2" section. If you've done so and it's still not working for you, please share a sample page showing the issue so we can look into it for you. (You can open a ticket here if you'd prefer to shared privately.) Thanks!

No, I don't have any news on this.

Yes, that's expected. You're using the "id" mode, so it shows the history of the file with the supplied ID across moves, including the revision of the file at each location where it is/was.

I see you're supplying a folder path and not a shared link and are using app authentication on this /2/files/list_folder call, which can cause this 'path/unsupported_content_type' error. When using app authentication, that is, with the app key and secret instead of an access token, you do not have access to an account…

The Dropbox Chooser doesn't offer a way to use an access token like that, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though.

Have you registered the correct domain in "Chooser / Saver / Embedder domains" on the app's settings page on the App Console for the app for the app key you're using?

If your app needs long-term access without repeated manual user interaction, the app should request offline access to get a refresh token. Refresh tokens don't expire by default (though they can be revoked on demand) so they can be stored and re-used multiple times over long periods of time without the user present. The…

This varies by endpoint. Most endpoints do accept file/folder IDs, but some do not. For example, listing, uploading, and downloads files can be done just by ID, but the tagging functionality can't. You can see which formats are accepted in the format string for the relevant parameter on any given endpoint in the…

@"corvettemina" As Здравко said, the user needs to authorize the app, at least once. For long-term access, you should now be using refresh tokens. The Java SDK can actually handle the refresh process for you automatically, as long as you supply the necessary credentials, e.g., as shown retrieved in this example (meant for…

The /2/files/download endpoint is a "content-download" style endpoint, so the file content is returned in the response body (not a header). Refer to your client's documentation for information on how to read the data from the response body.

The "http://127.0.0.1:52475/" address is the address of the local server that the OauthBasic and OAuthPKCE examples use to locally receive the redirect during the OAuth app authorization flow. Those are console apps designed to be run locally to show how to process the OAuth flow, and are not meant to be deployed as web…

That may not be helpful as we wouldn't be able to inspect or debug the code directly. I've put together a small sample project using the code snippets you provided here, just filling in the gaps as necessary. It doesn't reproduce the issue for me. (It retains the authorizedClient and can successfully make calls even after…

The file revision history doesn't follow a file when it is moved to another path. You can get the file revision history for a file across moves though by setting "mode" to "id" instead of "path" though. Refer to the /2/files/list_revisions documentation for more information.

The authorizedClient should only be nil if the clients were reset, or if after a relaunch the SDK wasn't able to retrieve the token from the Keychain. There isn't anything else you need to be doing to keep the authorizedClient available. Calling authorizeFromControllerV2 when you don't have an authorizedClient and need to…

There is a refreshAccessToken method, but you don't need to call that. (That's used internally, or if you want to switch to a smaller subset of scopes.) The SDK automatically performs the normal refresh process for you. It doesn't sound like that's the issue anyway though, as the local client wouldn't get set to nil if the…

Dropbox unfortunately does not support downloading the root folder like this, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. You'll need to specify non-root paths instead.

The "redirect_uri mismatch" error indicates that this call failed because the redirect_uri used on /oauth2/authorize, which is the redirectUri parameter on GetAuthorizeUri in the .NET SDK, to get that authorization code does not match the redirect_uri used when calling /oauth2/token, which is the redirectUri parameter on…

@"Kloss" The original "-u" option shown earlier in this thread is an option for curl for specifying the Basic credentials (which in this case should be the app key and secret). It looks like in your environment it was getting sent to Invoke-WebRequest, where "-u" is ambiguous. I'm glad to hear you already sorted that out.…

There isn't anything additional you should/can configure for this. Dropbox will automatically redirect through the flow when it can, but there are some exceptions. For example, it will only do so when an https:// redirect URI is supplied; it won't automatically redirect to http://. Also, if the user has linked accounts,…

As you mentioned, when processing the OAuth app authorization flow in an app using ObjectiveDropboxOfficial, SFSafariViewController is used. The web session in SFSafariViewController (such as whether the user is already signed in to www.dropbox.com) is separate from whether or not the ObjectiveDropboxOfficial SDK has any…

The Dropbox API doesn't offer a call specifically to just create an empty file, but you can call /file/upload with an empty body to make an empty file (that is, with a size of 0). A file with a size of 0 isn't a valid .docx file though, so if you mean you want to upload a valid .docx document that just doesn't contain any…

Thanks for clarifying. That's correct, the refresh process should be handled for you automatically as long as you've processed the authorization flow using authorizeFromControllerV2. Even if you did only have a short-lived access token stored though, or if the refresh process failed and the SDK wasn't able to get a new…

Can you elaborate on what you mean when you say "the connection is interrupted"? Do you get a particular error? If so, please share it here. Or, do you mean that DropboxClientsManager.authorizedClient just becomes nil at that point?

@"maxior" Здравко is correct. Additionally, you may find the File Access Guide and Detecting Changes Guide useful

A 413 error indicates that the request failed because the payload was too large. The filesUploadSessionFinishBatchV2 method in particular is a way to finish multiple upload sessions at once, and does not itself accept file data. That being the case, don't set 'contents' when calling filesUploadSessionFinishBatchV2.

Any user account can create and own multiple API apps. All of the apps owned by the currently signed in account can be found on the App Console.

To integrate with the Dropbox API from Java, we recommend using the official Dropbox Java SDK. You can find instructions and examples for using that there. Alternatively, you can use the HTTPS endpoints directly if you prefer. That documentation shows all of the details for the request/response formatting and parameters…

@"Pelleman" It is not possible to fully automate the OAuth process where the user chooses to authorize the app and the app then receives the resulting access token and optional refresh token. This needs to be done manually by the user once. It's not possible to programmatically get an access token or refresh token using…

@"vinke" Please print out the response body, as it should contain a more useful error message. While access tokens can be used to access multiple different endpoints, different endpoints do require different scopes, so it's possible that an access token can access one endpoint but not another. Also, be aware that just…