Greg-DB Dropbox Community Moderator

Yes, for the official Dropbox API v2 .NET SDK, you can find an example of using the new authorization functionality in the OauthBasic example (non-PKCE, meant for server-side apps) as well as in the OAuthPKCE example (PKCE, meant for client-side apps).

Yes, that "Could not create SSL/TLS secure channel" error indicates this is due to a problem establishing the secure connection between your client and the Dropbox API servers. Specifically, Dropbox recently retired support for TLS 1.0 and 1.1. The Dropbox API servers now only support connections using TLS 1.2. You'll need…

@"frebours" This is still open with engineering, but I don't have an update or timeline to share. I'll follow up here once I have any news.

1) Yes, follow the instructions under "How do I test my application?" on https://www.dropbox.com/developers/support to request a test team for testing the Dropbox Business API. That should give you a non-team-space team by default. 2) Yes, to list the team folders for a non-team-space team, you would use…

@"streetcodernate" Can you elaborate on what you mean when you say it isn't working for you? What error or unexpected output are you getting?

We don't have a video tutorial for OAuth, but I'll pass this along as a request for that. I can't promise if or when that might be done though.

Thanks for the report, and apologies for the trouble. We dropped support for .NET Framework 4.5 in v6.0.0 of the Dropbox .NET SDK, but it sounds like the configuration of the example app(s) weren't updated to match. I'll ask the team to update that accordingly to get those working again.

While Dropbox doesn't have any samples for Visual Basic in particular, you can find a number of resources for using the Dropbox API in the documentation. You may want to read through the Getting Started guide first.

Thanks for following up. I've sent this along as a request to eliminate those warnings, but I can't promise if or when that might be done.

[Cross-linking for reference: https://stackoverflow.com/questions/72060987/how-can-i-overwrite-a-file-using-dropbox-api-in-ios-swift#72060987 ] The upload method takes a 'mode' parameter, for which the value should be a Files.WriteMode, like this: client.files.upload(path: dropbox_upload_pathname, mode:…

The "team_data.member" scope is one of the team scopes available on the Permissions tab of an app's page on the App Console. There's currently a bug on our side with this configuration causing this issue though. We're looking into and I'll follow up here once I have an update on that.

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

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

Please have them contact us directly with the details of the issue then. (The status code itself isn't sufficient.) Thanks!

It sounds like you’re experiencing an issue with a third party application. Please reach out to the support organization for that app for help. If the developers of this app are having any trouble with the Dropbox API itself, they can reach out to Dropbox developer support directly with the relevant technical details.

[Cross-linking for reference: https://stackoverflow.com/questions/72054734/how-to-regenerate-expired-dropbox-access-token-of-customer-end-user ] Dropbox is in the process of switching to only issuing short-lived access tokens (and optional refresh tokens) instead of long-lived access tokens. You can find more information…

The /2/file_properties/properties/add endpoint is for adding custom file properties to existing files on Dropbox. To create/upload a file, you would use /2/files/upload first (or upload sessions for large files). Both of these identify the file using the "path" parameter. A 'path/not_found' error, such as from…

It sounds like you’re experiencing an issue with a third party application. Please reach out to the support organization for that app for help. If the developers of this app are having any trouble with the Dropbox API itself, they can reach out to Dropbox developer support directly with the relevant technical details.

@"Dinesh K" Здравко is correct, you'll need to make sure you're passing valid JSON in the request body for this call. We generally recommend using a JSON library to build that JSON to make sure it's valid. You can also use the API Explorer for testing/prototyping such calls.

Update: the Dropbox Saver should now work in Chrome on iOS.

Update: the Dropbox Chooser should now work in Chrome on iOS/iPadOS.

It's not possible to exchange a long-lived access token for a refresh token, however it is not necessary to make existing connected users switch anyway. Existing long-lived access tokens can continue to be used, as we don't currently have a plan to disable existing long-lived access tokens. (If that changes, we will of…

Thanks for the report! I'll ask the team to look into it.

Thanks for the note. This is open with engineering. I'll follow up here once I have news.

Are you using an app key for an app that hasn't been migrated to scopes yet? This can occur if so. (Apologies for the unhelpful error message!) In order to use the updated app authorization flow, you'll need to use an app key for an app that is set to use scopes. You can migrate an existing app to scopes via the app's page…

The Dropbox API doesn't offer a way to detect the presence of other users potentially editing a file via the API at the same time, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. Check out the Detecting Changes Guide for ways to detect when changes have been…

@"Bamante" It sounds like dsagal is referring to the browser's console, sometimes called the JavaScript console. (Refer to your particular browser's documentation for information on how to access it if you wish.) On a page where the Embedder is currently failing, that console is currently showing some errors. We're looking…

Thanks for the report! We'll look into it and follow up here with updates.

It's not clear if those settings mean that Invoke-RestMethod will use TLS 1.2. I can't offer help specifically for Invoke-RestMethod as it's not made by Dropbox, so I recommend referring to its documentation for information on configuring it.

Can you elaborate on what you mean when you say "the PCs are running TLS 1.2"? Can you check if 'Invoke-RestMethod' in particular is using TLS 1.2 for these network requests? The Dropbox API servers do currently only support TLS 1.2, so it would be fine to enable only TLS 1.2 client-side for this as far as the Dropbox API…