Greg-DB Dropbox Community Moderator

The 'Microsoft.PowerShell.Commands.WriteErrorException' error type isn't made by Dropbox, so I can't offer too much insight on that. If a Dropbox API call fails, the Dropbox API would return a response body, but I don't see one here. I do still expect this is related to the TLS change though, so I recommend looking into…

@"Tech Dev Oldsmar" Thanks for pointing that out! I'll ask the team to improve that example.

@"Tech Dev Oldsmar" It looks like you have the right idea here; you're grabbing the Retry-After from 'e.ErrorResponse.RetryAfter'. (Exactly how you structure your app with respect to exception messaging and thread handling is up to you though. E.g., it seems like in your sample you wait and then re-throw the exception.) I…

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

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

@"production_tvox" Здравко is correct; retrieving new long-lived access tokens is no longer an option. Refer to their message and the thread they linked to for more information. By the way, I just checked and I see that your support ticket #16503714 did get a response with information about this. If you did not receive…

I'll be happy to help with any issues you're having with the Dropbox API, but I'll need some more information. Please reply with: * the name and version number of the platform you are using * a sample of your "ver" variable, if you can share it publicly, or otherwise a redacted version showing the hostname at least * the…

Thanks for following up. I'm glad to hear you got this working already. For reference, it sounds like you're using an app key for an app that hasn't been migrated to scopes yet. This can occur if so if you request scopes. (Apologies for the unhelpful error message!) In order to use the updated app authorization flow to…

@"Danut" A TLS issue would fail earlier in the connection process, with a different kind of error. A 'missing_scope' error indicates that while the app is permitted to use that scope, the particular access token you're using to make the API call does not have that scope granted. Also, be aware that just adding a scope to…

@"Mostafa Ezzat" I see Здравко very helpfully offered a detailed walk-through of this flow. Please let us know if this still isn't working for you.

I see you're getting an error "Could not create SSL/TLS secure channel.". That confirms that this is happening because 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 to update your app/network client/environment to use TLS 1.2 in order…

The REFRESH_TOKEN value should be the 'refresh_token' returned by /oauth2/token when you called /oauth2/token with 'grant_type=authorization_code'. That's different from the 'access_token'; the two are not interchangeable.

The authorization code can only be used once. Once you use it to get an access token and optional refresh token by calling /oauth2/token with 'grant_type=authorization_code', you can throw away the authorization code and store and re-use the access token and optional refresh token instead. You can use a refresh token to…

Whenever you make an API call, such as to /2/files/upload like in this code, you would either get a response from the API (such as the result or some API error), or some error from your network client if the connection failed. I understand you're not getting an error message in the output, so you may need to debug this or…

Dropbox doesn't offer a step by step tutorial for this exactly, but perhaps you can elaborate on what you need to do at a high level, what you have so far, and what exactly isn't working. For instance, in your first post you mentioned you needed to update your app from TLS 1.0 to 1.2. Does that mean you already had some…

I see you're not setting a redirect_uri on /oauth2/authorize, so you should also not set a redirect_uri when calling /oauth2/token. Remove that '-d redirect_uri=...' from your /oauth2/token call and try again. By the way, as a matter of security, do not post your authorization code or app secret.

This appears to be a follow up to your earlier thread. I'm afraid I don't have much to add to that. All of the official resources for using the Dropbox API from .NET are part of the official Dropbox .NET SDK, but it sounds like that SDK isn't suiting your needs. (You can of course call the Dropbox API HTTPS endpoints…

Thanks for following up. Unfortunately in this particular case this doesn't appear to be sufficient for me to investigate. Can you please open a ticket here from the affected account, and also let us know the relevant app name, so we can look into this internally? Thanks and apologies for the bother.

It sounds like your team now uses the "team space" configuration. You can access the team space via the API, but you'll need to set the 'Dropbox-API-Path-Root' header to do so. You can find information on this in the Team Files Guide.

Unfortunately Dropbox doesn't currently have an example like this for UWP posted, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though.

The "redirect_uri mismatch" error indicates that this call failed because the redirect_uri used on /oauth2/authorize to get that authorization code does not match the redirect_uri used when calling /oauth2/token. These two values need to match exactly. Or, if you didn't set redirect_uri on /oauth2/authorize, you should…

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 on this migration here. Apps can still get long-term access by requesting "offline" access though, in which case the app receives a "refresh…

The "Access to a closed stream is not possible" error message doesn't appear to be coming from the Dropbox API itself, so I can't offer too much help with that in particular. That said, it's likely referring to that "memStream" object. It looks like that's closed, since it was used in the first attempt, so you'd need to…

We don't have video tutorials for the API/SDKs, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. The "LoopbackHost" in the example is the address of a local server, defined by the app, used for the redirect URI for the OAuth app authorization flow. That's where the…

Thanks for the report. Can you share several X-Dropbox-Request-Id values for these failures? They're safe to share publicly, but you can open an API ticket here if you'd prefer to share privately.

No, Dropbox no longer offers the option for retrieving new long-lived ("no expiration") access tokens. You can find more information on this migration here. Instead, to get long-term access, apps should request "offline" access, in which case the app receives a "refresh token" that can be used to retrieve new short-lived…

In the code snippet you shared, "authorize" and "token" are just strings used as URL paths on the local server used to handle the result of the OAuth app authorization in that example app.

I see, thanks for the context. That expiration only applies to the access token. You can find more information on each field in the documentation here.

No, the Dropbox Chooser does not offer an option for getting the name of the parent directory of the selected file. You can find all of the available options in the Chooser documentation.

@"marksmithhfx" It looks like the use of POST for these requests is required in the OAuth 2 specification: The client MUST use the HTTP "POST" method when making access token requests. I'll send this along as a feature request to support GET as well, but I can't promise if or when that might be implemented (especially as…