Greg-DB Dropbox Community Moderator

The Dropbox web site has recently dropped support for Internet Explorer 11. You can find the official system requirements here. Please note that API apps should not be processing the OAuth app authorization flow in a web view, per the /oauth2/authorize documentation. Please update your app to use the system browser instead.

The startOAuth2Authentication method uses the old flow, which currently gives legacy "long-lived access tokens", which don't expire by themselves. Note that starting September 30th, 2021 Dropbox will no longer return new long-lived access tokens, so you should switch to the new flow. The startOAuth2PKCE uses the new flow,…

Are you referring to a file extension on fileResponse.File? That would be under your control, not a matter of the Dropbox API/SDK. For reference, the Dropbox SDK just returns the file data as a stream from GetContentAsStreamAsync(), not file metadata, such as the file name and extension. If you want the file metadata, you…

@"jenkinspps" Thanks! That's helpful. We'll look into it and I'll let you know when I have an update on this.

You can find information on how to migrate to the new functionality in this post. Please also refer to the OAuth Guide and documentation. Note though that these resources only refer to the Dropbox API itself. The two libraries you linked to are made by third parties, so I can't offer guidance on what functionality they do…

If you step through with a debugger, where exactly in the code does this stop behaving as expected? Also, how big is the file you're trying to download, how long does the (incomplete) download take, and that's the final size of the (incomplete) downloaded file?

No, it's not possible to switch a user to short-lived access tokens/refresh tokens from long-lived access tokens without user interaction. We don't currently have a plan to disable existing long-lived access tokens though. (If that changes, we will of course announce that ahead of time.) That being the case, your users can…

@"jenkinspps" Can you share a few sample X-Dropbox-Request-Id response header values for the issue you're currently seeing? Thanks in advance! 

We responded to that ticket on Wednesday. Please check the email inbox for the email address on the account used to open that ticket for the response. If you don't see it, please check the spam folder too.

We replied to your support ticket yesterday. Please check the inbox for the email address on the account that owns the app for more information. 

You should use the startOAuth2PKCE method instead of startOAuth2Authentication now. You can find an example here: https://github.com/dropbox/dropbox-sdk-java/blob/3162efeccaca247e25553acd21f6ac0bf9018ad6/examples/android/src/main/java/com/dropbox/core/examples/android/DropboxActivity.java#L94

No, unfortunately Dropbox doesn't offer the ability to set/get the API file properties/templates via the official Dropbox user interfaces, such as the desktop client or web site, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. 

The SDK should handle the refresh for you automatically. Can you double check that you have the correct access token, refresh token, app key, and app secret values though? For instance, you need to use the same app key and app secret you used to originally get the refresh token in order to use the refresh token to get a…

@"OFV" When your "DropboxClient is instantiated with the Access_token and refresh token", are you also supplying the app key and secret? Those are required to perform the refresh. Make sure you're doing so, like in the example here.

Even if the folder is empty, the folder itself would have a path, but again it would only be returned if the accounts match. We'll look into it and follow up with you on your ticket.

This behavior sounds unexpected, so please open an API ticket from the account that owns the affected app so we can investigate. Please include: * the name or key of the affected app * the affected webhook URI * a sample timestamp of when this occurred Thanks!

Yes, using sharingGetSharedLinkMetadata is the right way to get the corresponding path just based on the shared link. If that's not working properly for you, please share a sample so we can look into it. For instance, share the output of both usersGetCurrentAccount and sharingGetSharedLinkMetadata, as well as the shared…

Apologies for the confusion. You can start a concurrent upload session in the .NET SDK by passing an empty body, like this: var uploadSessionStartResult = await _client.Files.UploadSessionStartAsync(sessionType: UploadSessionType.Concurrent.Instance, body: new MemoryStream()); I'll ask the team to see if we can update the…

Thanks for writing this up and sharing the context. Unfortunately, no, I don't believe the Dropbox .NET SDK offers a way to retrieve the current short-lived access token like this, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. 

How are you checking that you're using an access token for the same account as the one that made the shared link? I just tried this functionality and it is working for me. When using the same account, I get the path_lower value. You can use the usersGetCurrentAccount method to check what account a particular access token…

Thanks! I was on an older version where it does work in Chrome, for whatever reason. I'll ask the team to look into that variant as well.

Thanks for the post. Unfortunately, that behavior is expected sometimes, and there isn't a way to just prevent it. The original casing isn't always available for all components. There's a note about this in the API v2 documentation, under "Case insensitivity": Also, while Dropbox is case-insensitive, it makes efforts to be…

Thanks for the post. While the Dropbox Chooser for Android isn't officially marked deprecated, it hasn't been updated in several years. I'll send this along as a request to either update that or officially deprecate it.

@"OFV" The Dropbox client in the SDK can and will automatically handle the refresh for you, and you shouldn't even need to access to refresh token or new access token after a refresh. The refresh token doesn't change, and the client will automatically set its new access token. And if you need another client, you can just…

@"ozdev" This is open with engineering, but I don't have an update on it yet. I'll follow up here once I do.

This seems to be a duplicate of this thread. Please refer to that for more information.

When you say "the user account that I used is an authenticated user dropbox account.", that doesn't necessarily meet the requirement. In order to receive the path_lower value, the account for the access token you're using to make the call needs to be the same account as the one that created the shared link.

I'll be happy to help with this however I can, but I could use some more information. Can you share: * the HTML/code you're using on your page for the Embedder * what, if any, unexpected error/output you get in the JavaScript console on your page * the URL to a sample page showing the issue Feel free to open a ticket here…

@"phbd" No, unfortunately I don't have an update on this request right now.

The SharingFileLinkMetadata.path_lower (as returned by sharingGetSharedLinkMetadata) is "only be present only if the linked file is in the authenticated user's dropbox.". So, it sounds like the linked file doesn't exist in the account that you're connected to. In that case, you'd need to supply the path yourself. For…