Greg-DB Dropbox Community Moderator

Apologies, no news on this right now.

@"Thibaut D." No, unfortunately I don't have an update on this request.

Thanks for the post! The Dropbox API doesn't offer anything quite like this unfortunately, but I'll pass this along as a feature request.

Thanks for writing in. Note that the first error is because non-root paths should start with a '/'. So, your path there should be "/testFolder", not "testFolder". The root path is identified by the empty path "". The second error did start occurring with recent changes to the requests dependency. We're looking into that.…

For /2/files/list_folder, the path is whatever path in the account you want to list. To list everything, you would use the empty string "" to identify root. For /2/files/list_folder/continue, the cursor is the last cursor your received from /2/files/list_folder or /2/files/list_folder/continue for that user. (You'll need…

Yes, that's correct, for OAuth 2 at least. (API v2 doesn't support OAuth 1 so I expect it will make sense to shut down the OAuth 1 endpoints along with API v1 itself.)

To keep track of changes in the accounts of the users linked to your app, you should start by calling /2/files/list_folder and /2/files/list_folder/continue as necessary, following the instructions in the documentation to get the full state of the account. With each call, you should store the latest returned "cursor". The…

The Dropbox Saver doesn't support blobs, local files, or data URIs unfortunately, but I'll pass this along as a feature request.

If you're not using an official SDK, the easiest way to check what version of the API you're calling is to check the URLs you're calling. API v1 endpoints contain "/1/", while API v2 endpoints contain "/2/". (Note that some OAuth URLs also contain "/1/" for historical reasons, but those aren't considered part of API v1…

The user can link multiple apps to different accounts. They may need to sign in/out of dropbox.com though, as necessary, since you can only link an app to an account when signed in to that account. Once they do so though, they don't need to re-authorize each time they use the app. Each app will receive an access token for…

To follow up here, the latest version of SwiftyDropbox does now have support for the 1Password extension in the app authorization flow, by virtue of now using SFSafariViewController, which automatically has access to extensions.

Thanks! We'll look into it. Note that is is important that your app process these entries in order. Otherwise, you may not get a state consistent with the state on the Dropbox servers.

The user can still choose which account they want. On Mac, the app authorization flow uses the normal /oauth2/authorize desktop web page, so they just need to sign out of the currently signed in account, if any, and then sign in to the desired one. There's a "Sign out" option in the dropdown in the top right of the page.

Yes, a normal structured error is expected for these API v2 endpoints we were discussing. It looks like you may be calling API v1 though (i.e., /1/team), based on the error messages you shared. Can you check if that's the case?

That should be a string that identifies your app, generally your app name and app version. You can find more information here under newBuilder: https://dropbox.github.io/dropbox-sdk-java/api-docs/v3.0.x/com/dropbox/core/DbxRequestConfig.html#newBuilder-java.lang.String-

Yes, if you're using the official API v2 Java SDK, you can set a proxy by constructing a StandardHttpRequestor with a StandardHttpRequestor.Config. You can build a StandardHttpRequestor.Config with a proxy set by using StandardHttpRequestor.Config.builder to get a StandardHttpRequestor.Config.Builder and using…

The sharing_info field will only be set if the file is inside a shared folder. It sounds like this file is no longer in shared folder, so it won't be set anymore. (For example, you may have "left" the shared folder, but kept your copy.)

Regarding the errors reporting by @"thedeck" and @"sfbrad", these 500s can be caused by certain file metadata not being available yet, at the time of the API call. The team has been working on improvements around this. When this information is still not available, Dropbox will now be returning 429s, to instruct the app to…

Thanks for the report! I'm seeing the duplicate "/oldname" in my testing, but not the extra deleted "/newname", though I expect it will depend on the particular state of the account. In this sample, did you previously have anything at "/newname" by any chance? We'll look into whether or not we can clean this up, but the…

The API v2 Java SDK works a little differently than the v1 SDK, so there isn't a direct equivalent. The isLinked method could be called on the Session object to determine if it had an access token, but the v2 SDK doesn't have an equivalent session object. Instead, you can should just check if you have a DbxClientV2 object.…

[Cross-linking for reference: https://stackoverflow.com/questions/44173750/system-configuration-configurationerrorsexception-was-caught-during-uploading-fi ] I redacted it for you, but for the sake of security, you should disable that access token that you posted. You can do so by revoking access to the app entirely, if…

Quick update here, the email now includes the app name, so this should be less confusing for users. Hope this helps!

That version of the SDK does use API v2, so it sounds like it is just users with an old version of your app. One exception for the Java SDK in particular though is that it does still contain API v1 functionality (for now) to ease the migration. Just make sure you're not using DbxClientV1 anywhere in your latest code.

Hi Jan, I believe this is supposed to already work. The SDK contains PCL with profile111 which is compatible with .NET Standard 1.1 and above. Can you share the steps you followed to reproduce this, and the full error/output you're getting? Thanks in advance!

For these calls with the parameters in the header, you need to escape these characters. That is, when you use the “Dropbox-API-Arg” header, you need to make it “HTTP header safe”. This means using JSON-style “\uXXXX” escape codes for the character 0x7F and all non-ASCII characters. Some, but not all, languages/libraries do…

The latest release is actually 3.1.0, not 3.0.15. Please update to that, as there have been some fixes that may be relevant here. (Also, are you sure you updated to 3.0.15? The 'response' method was renamed to 'setResponseBlock' in 3.0.0.) If the issue persists with 3.1.0, we can look into this with you. To clarify though,…

I'm not sure I follow. If you call getCurrentAccount you can get Account.profilePhotoUrl which is a URL to the profile picture. If that's not what you're looking for, can you elaborate?

Thanks for the post! Unfortunately, it's not possible to use the Chooser via an OAuth API authorization like this, but I'll be sure to pass this along as a feature request.

Even if you've already migrated your app to API v2, it's possible you got the email if some users are still using old versions of your app. Exactly how you check what version you're using depends on what SDK, if any you're using. Are you using one of the official SDKs? If so, which one and what version number?

Thanks for the feedback @"tim". I'll bring this up with the team again. By the way, we are now reviewing requests for extensions to API v1 access. If you'd like an extension for access to API v1, please open an API ticket and include: - The app key(s) for the app(s) you need an extension for. - The reason(s) for the…