Greg-DB Dropbox Community Moderator

I'm not sure exactly what you were trying to build with that code, but no, you should not be attempting to programmatically access the Dropbox web site like that.

@"MiNJ" Thanks for the feedback! I'll send this along with the request.

1. When using the Dropbox API, such as via the official Dropbox API v2 Java SDK, to upload a new version of a file, the app needs to upload the entire new version of the file. The API does not offer a way to upload only the changed portion of a file, but I'll pass this along as a feature request. I can't promise if or when…

In order to get an access token (and optionally a refresh token) for an account, your app should implement the OAuth app authorization flow. You can find information on how this process works in the OAuth Guide and authorization documentation. In your code snippet here, you seem to be attempting to access the Dropbox web…

Thanks for the report. This is open with engineering. I'll follow up here when I have an updates on this.

We don't have any support or resources for Vue in particular, but there are some TypeScript examples for the official Dropbox API v2 JavaScript SDK, in case that helps.

You are not required to change the "Access token expiration" setting for your app. If you do not change it, existing users on old versions of your app will continue using the old flow, and users on the updated version of the app will use the new flow. If you do not change it, nothing will change for old versions of your…

The /2/files/download endpoint is a "content-download" style endpoint, meaning that when the call is successful, the requested file data is returned in the response body. It sounds like that is what you're seeing. That is, the text you're reading out is the raw file data. What you do with that data is up to you. For…

Thanks for writing this up! Unfortunately the Chooser doesn't offer a way to do either of these, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. 

Thanks for the post. Unfortunately, I don't have a good solution to offer here. The API doesn't offer a way to control the parsing of search queries like this, or a way to perform strict/exact matching like you're looking for, but I'll pass this along as a feature request. I can't promise if or when that might be…

Thanks! I'll also ask the team to clarify that error message to distinguish between PKCE and non-PKCE. 

Dropbox does not currently have plans to change the redirect URI requirements when using the standard 'response_type=code'. You should be able to use a custom URL scheme like this when using the PKCE flow in particular though. You can find more information on using that in the authorization documentation and OAuth Guide.…

I'm not sure exactly what scenario you're running in to here. Can you share the output of these API calls so I can take a closer look? It may be easier to use the API v2 Explorer so you can see the API responses directly.

This should be fixed as of v6.0.1 of the SDK.

Would you be able to share the relevant code and output for this so we can take a closer look? Be sure to redact your access token though. Also, how and when was the file deleted originally? Feel free to open an API ticket if you'd prefer to share privately. Thanks!

@"johndoe5" Здравко is correct, the page size of a result from /2/files/search_v2 and /2/files/search/continue_v2 is not guaranteed, and may be empty in some cases like this, due to how the Dropbox search functionality works. Your app should be written to call back if 'has_more' is true, but be able to handle empty…

Thanks for following up. This is open with the team as a request for detailed documentation for this for the SDKs in particular. I'll follow up here with any updates on that.

Any users using old versions of your app will continue to be able to use it without issue for now. Once you switch the "Access token expiration" setting for your app on the App Console to "Short-lived", or on September 30, 2021, whichever comes first, users using old versions of your app should still be able to use it, but…

You can find links to the relevant documentation and guide inline in my first message on this thread here.

It sounds like your team is set up to use the "team space" configuration, so you shouldn't use the /2/team/team_folder/* endpoints. To create a folder in the team space, you should use the /2/files/create_folder_v2 endpoint. Please refer to the Team Files Guide for information on how to operate in the team space. 

Thanks for following up. Yes, the file names for files uploaded to Dropbox via the Dropbox API are set by the app's code when it performs the upload, so you'll need to contact them for help with that. They can contact us directly if they do need help with anything on the Dropbox API itself of course.

Dropbox no longer offers the creation of "legacy" API apps, only "scoped" apps. Scoped apps can access all of the same functionality that legacy apps can though (by enabling the relevant scopes), so you don't need to create new legacy apps. Scoped apps just offer more granular control over what functionality the app can…

Thanks for the additional feedback!

Thanks for clarifying. Yes, in that case you'd need to use the API since the Chooser doesn't support selecting the root itself.

In your subject, you seem to be referring to the "Dropbox Chooser", which is a pre-built way for developers to easily allow their end users to choose files or folders from their Dropbox accounts to give to the third party app. If you're interested in using that, you can find more information here. From your description…

That error generally indicates that you don't have the relevant domain registered for your app in "Chooser / Saver / Embedder domains". You mentioned you registered "localhost", but are you actually running it on localhost? What's the URL of the page where you're trying to display it? You can also check the JavaScript…

The "Automatic time zone" setting applies to the Dropbox UI, not the Dropbox API. The Dropbox API uses UTC for file metadata, and API clients can then format times to display them in whatever format and time zone desired. By default, the Dropbox API returns two pieces of time information in the standard file metadata for…

The Dropbox API unfortunately doesn't offer the ability to get starred files, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. 

Unfortunately, Dropbox does not offer an API or way to programmatically manage the official Dropbox desktop client, such as to pause or resume syncing, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. One exception is that the Dropbox desktop client on Linux only…

You can certainly use the API to upload files instead (files_upload for files smaller than 150 MB, or upload sessions otherwise). That would be helpful in that the code would directly know when the file is completely uploaded. That's not strictly necessary though. You can use other functionality on the API to detect…