Greg-DB Dropbox Community Moderator

@"marksmithhfx" We started rolling that out on or after April 13 of last year, so if this was more recently working for you, that may not be the cause.

@"marksmithhfx" As Здравко noted, that's not an error message/code from Dropbox itself, so I also suggest referring to the documentation for your client/platform. For reference, they mentioned TLS 1.2 as the Dropbox API only supports TLS 1.2 (and not TLS 1.1, or lower, for example). The error does mention SSL, so make sure…

The /2/files/download_zip endpoint is only meant for downloading folders from Dropbox, not files. (Dropbox zips the folder into a zip file on the fly for that.) To download a file (whether the file is a .zip file or not), you would use the /2/files/download endpoint instead. Also, it looks like your `path` value might be…

We've released a beta version of SwiftyDropbox with some significant updates, such as to remove the dependency on Alamofire. You can find more information here: https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Beta-version-of-major-SwiftyDropbox-update-available/td-p/695441

We've released a beta version of SwiftyDropbox with some significant updates, such as support for background sessions. You can find more information here: https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Beta-version-of-major-SwiftyDropbox-update-available/td-p/695441

While refresh tokens can be used repeatedly and don't expire automatically, they can become invalid at any time for a number of reasons (for example, if the user or app revokes it using the https://www.dropbox.com/account/connected_apps web page or the /2/auth/token/revoke API endpoint). If/when a refresh token is revoked,…

This should be working again now. Please let us know if you're still seeing any issues. Thanks!

This should be working again now. Please let us know if you're still seeing any issues. Thanks!

This should be working again now. Please let us know if you're still seeing any issues. Thanks!

This should be working again now. Please let us know if you're still seeing any issues. Thanks!

Thanks, yes, we're aware of and are investigating this issue.

Thanks for the report! We're looking into it. I'll follow up here once I have an update for you.

Thanks for the report! We're looking into it. I'll follow up here once I have an update for you.

Thanks for the report! We're looking into it. I'll follow up here once I have an update for you.

As noted in the other threads you found, the /2/files/upload Dropbox API endpoint is a "content-upload" style endpoint, meaning it expects the file data in the HTTPS request body. The data should be sent just as a raw octet-stream (per the "Content-Type"), without any additional encoding. (Dropbox doesn't perform any…

@"Anonymous One" I see you also posted your own thread, so we'll follow up with you there.

@"Anonymous One" I see you also posted your own thread, so we'll follow up with you there.

@"Thang2000" Thanks for letting us know! I've updated the links in my previous post.

Yes, it's generally best to use /2/files/move_batch_v2 when you have multiple items to move/rename. Otherwise, there isn't a way to improve the speed of these operations on the API, but I'll pass this along as a request. I can't promise if or when that might be optimized though.

It is not possible to increase the permissions (e.g., add another scope) on an existing access token or refresh token. Adding a scope to your app via the App Console does not retroactively grant that scope to existing access tokens or refresh tokens. That being the case, to make any API calls that require that scope,…

The Dropbox .NET SDK is not built or tested for official support Maui or Xamarin, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though.

The Dropbox API does have a general rate limiting system that applies the same to all account types and API endpoints, but we don't have specific rate numbers documented for that, and we cannot increase the limits for any particular app, user, or team. Apps should be written to handle these rate limit responses…

@"jacky-radix" As Здравко said, webhook URIs are registered for apps, not accounts. Webhook notifications will only be sent for changes in accounts connected or "linked" to that app. If you haven't linked your account to your app, you won't receive webhook notifications for your account. I suggest reading the OAuth Guide…

@"Ivan_" For reference, does that flow in the original sample app work for you though? I highly suggest trying that out to make sure that works and see the flow processed fully before trying it out in your own code. In any case, when using a redirect URI, Dropbox will redirect the user's browser to the specified redirect…

@"iconify" These list_folder cursors do not expire by default, so they could last that long. However it is possible for them to become invalid at any time, due to some kinds of operations in the account, at which point /2/files/list_folder/continue would return a 'reset' error. That being the case, make sure your app is…

@"Babaraba Abdabi" As Здравко mentioned, you shouldn't assume that a link constructed like that will be necessarily correct always. We don't officially support building links like that; I recommend trying out the 'no_one' shared link option that I mentioned and that Здравко reiterated, as it sounds like it would be useful…

@"dragon v2" Здравко is correct; you should use the endpoints they linked to (or corresponding SDK methods) to list the contents of a folder. The File Access Guide may also be a useful reference.

@"rahulj1" You'll need to write and test your own code to suit your particular use case, but it might look something like this: import dropboxdbx = dropbox.DropboxTeam(ACCESS_TOKEN).as_user(TEAM_MEMBER_ID)root_namespace_id = dbx.users_get_current_account().root_info.root_namespace_iddbx =…

There are a number of different things that can cause that error. Did you check everything listed in my previous message? Have you tried running the example code without modification first?

This error indicates that the application's code has not been implemented to support long-term access properly. This is something the developer of the third party application will need to update the code to accommodate. This isn't something you can configure as the end-user of the app.