Greg-DB Dropbox Community Moderator

As long as the app allows you to re-connect the Dropbox account, you should still be able to use the integration for up to four hours at a time. Also, any data in your Dropbox account should still be there and accessible to you via Dropbox directly, e.g., www.dropbox.com, though that may or may not be useful depending on…

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…

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 your app via the App Console does not retroactively grant that scope to existing access tokens or…

I'm sorry to hear about the issues you're having with this third party app, as well the trouble contacting the makers of the app. For reference, it sounds like the app is not handling short-lived access tokens properly. This is something that the third party app would need to be updated to handle. If the developers of this…

Thanks, that's helpful. It looks like your jistix-staging.com/oauth2/dropbox page is itself redirecting back to www.dropbox.com for some reason. It goes by fast in the log in your video, but here's the relevant portion: The authorize_submit page is the "Allow" action on the Dropbox app authorization page, which returns a…

Thanks for the report. This issue doesn't seem to reproduce for me though. Can you perhaps share a short screencast showing the issue? It may help to open the Network tab of the browser's developer tools first so we can see what requests are occurring.

@"LouisCorleone" Yes, that's correct. The Dropbox API still doesn't offer a way to retrieve this value directly.

@"Jistix_" You can work around this by disabling the 'files.permanent_delete' scope for your app on the App Console. (Of course, that's only suitable if you don't need that scope.)

Thanks for writing this up! I'm sending this along to the team to see if we can get this supported. I can't promise if or when that might be done though.

No, unfortunately I don't currently have a mechanism or documentation to offer for that; this is open with the team, but I don't have a timeline on if/when this would be done.

It's not possible to get a refresh token from an access token. A refresh token can only be retrieved by authorizing the app via the OAuth app authorization flow. (The "Generate" button on an app's page on the App Console does not offer the ability to get a refresh token; that only returns an access token.) To get a refresh…

Apologies for the confusion. The file sharing functionality offered by /2/sharing/add_file_member and /2/sharing/update_file_member does not support AccessLevel.editor for all file types. If you want to add editors to a file, you can instead put the file in a folder and share the folder via /2/sharing/share_folder,…

@"mayuri_thakare" Здравко is correct, this endpoint doesn't support "app folder" apps. You can find more information on the different permissions here. If you need to use this endpoint, you'll need a "full Dropbox" app instead. It's not possible to change that for an existing app, but you can register another app here.

@"Dmitri Bugryshov" Thanks for the note. This is open with engineering and I'll follow up here once I have an update on it.

@"xwbash" I see Здравко helpfully linked to some useful information. Let us know if you're still having any trouble.

Thanks for the report! I'm sharing this with the team to see if we can clean that up, but I can't make any promises myself. I'll follow up here with any updates on that.

Thanks for the report. This looks like a bug on our side with this configuration. We'll look into and I'll follow up with you here once I have an update on that for you.

@"dwissing" Здравко is correct, and offered helpful guidance, so please refer to that. Also, note that refresh tokens don't expire, so you can store and re-use them repeatedly.

@"qa7641" Dropbox still doesn't offer support for using the Dropbox Chooser in Angular, but I'll pass this along as a feature request. I'm not aware of any plans for that currently though.

Dropbox does not throttle connection speeds like that. While Dropbox has a rate limiting system in place, that operates on the basis of calls per time period, and any rate limited calls would result in a specific error, not limited connection speed. Also, an app's development/production status does not affect connection…

@"knoppys" As Здравко mentioned, you're missing a leading slash in the path you're showing here, so this call would fail anyway, and would not upload anything. If you are successfully uploading something, e.g., with a different version of this code, though, can you clarify where/how you're seeing the unexpected "&"?

The Dropbox OAuth functionality can be used for any number of users, so this works the same way if there are multiple Dropbox users, or just one. If you're the only Dropbox user, you'd just process this once to get your own refresh token.

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…

Check out the Performance Guide for some optimizations you can make to upload in a performant manner. Additionally, for uploading large files, check out the new "concurrent" UploadSessionType option, which lets you upload multiple pieces of a single file/upload session in parallel. There's also a new…

Apologies for the delay, the Embedder should be working again now. Please let us know if you're still seeing any issues. Thanks!

Great, I'm glad to hear that fixed it. And yes, the refresh token doesn't change or expire, and can be re-used multiple times. When you pass it to the DropboxClient like this, the client will automatically perform the refresh to get a new short-lived access token whenever needed, without you needing to do anything extra.…

An 'invalid_grant' error can indicate that the values you're supplying to ProcessCodeFlowAsync don't match the configuration used with GetAuthorizeUri to get that particular authorization. For instance, I see you're using a redirect URI ('new Uri(RedirectUri)') with GetAuthorizeUri. In that case, you need to supply that…

It looks like our messages just crossed. I'm glad to hear you already sorted this out, and thanks for the feedback!

Can you share the full error output for reference? Looking at the screenshots though, I do see two things that should be corrected: * You should use POST instead of GET. * The /2/check/user endpoint is an RPC-style endpoint, so you should supply the API parameter ("query", in this case) in JSON in the request body, not as…

No, when requesting "offline" access, the app receives a "refresh token" that can be used to retrieve new short-lived access tokens whenever, without manual user interaction (that is, the user doesn't need to repeatedly re-authorize the app once the app has the refresh token). The .NET SDK will perform that refresh process…