Greg-DB Dropbox Community Moderator

@"siddharth chauhan" Yes, you're correct. The app should use the latest returned cursor, which would be result.cursor there.

What error, if any, do you get in the JavaScript Console when you try this? From what I can see, it looks like it may just be a syntax error. You're missing a comma here: // view: "list" // or "grid" It should be: view: "list", // or "grid"

Thanks for the report! It looks like there was a bad configuration on our side preventing you from loading that. I just fixed that so it should work again now. Please try again and let me know if you still see any issues. Thanks and apologies for the inconvenience! 

No, unfortunately there isn't a way to upload an entire folder at once; you'll need to upload each file as you described. I'll pass this along as a feature request, but I can't promise if or when that might be implemented.

Thanks for the detailed feedback! I'm sharing this with the team.

Thanks for the report! I just gave this a try on macOS Catalina with Xcode 12 GM though, and it didn't fail for me. Can you let me know what your Cartfile look likes and what version of Carthage you're using? Edit: disregard this. I can reproduce this issue now. It looks like my Carthage was still using an old version of…

I'm glad to hear you got this working well. I can't share any guidance on the rate limiting parameters though, as we try not to encourage apps to rely on hard-coded limits, as the system can change over time. So, make sure your app is still able to always check and use the returned Retry-After value.

I'm not sure I understand your latest message. Can you clarify? Alternatively, if you have questions about Dropbox file restorations and version history retention in general, you can contact support directly.

You can get an API app key and secret (a.k.a. consumer key and secret) by creating a Dropbox API app at: https://www.dropbox.com/developers/apps/create Once you have an app created, the app key and secret will be available by going to the App Console and selecting the app here: https://www.dropbox.com/developers/apps

We did recently add a "completion" parameter. You can find the updated usage with that in the readme here, or in the docs here. Can you link me to the pages you found showing the old usage? I'll ask the team to fix those up. Thanks!

Dropbox doesn't offer an SFTP interface, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. Dropbox does offer an API that works over HTTPS though that you can use to programmatically upload and download files, among other operations. You can find everything you need…

@"tribalneck2000" All of the functionality discussed above is available both via the API v2 HTTPS endpoints themselves, as well as the official Dropbox API .NET SDK. 

@"GevorgMel" This functionality should now be available on DropboxTeamClient as of release v5.1.0. Please update and give that a try and let us know if you run in to any issues. Thanks!

Unfortunately I don't have any specific rate limit numbers to share.

Thanks for sharing this. First, please note that you should not use a webview for the Dropbox app authorization flow, per our /oauth2/authorize documentation. As for the issue, it looks like it's because it's using an old browser engine, e.g., an old version of Webkit. Unfortunately that is not officially supported by the…

Unfortunately, the Dropbox API doesn't currently offer a way to update Paper docs that are stored as .paper files, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. (The paperDocsUpdate method only works for legacy Paper docs, not in the filesystem as .paper files.)…

I just tried running a stripped down version of this code in the same environment (using v5.0.0 of the Dropbox .NET SDK, in a project using VB.NET and .NET Framework 4.6.1 in Visual Studio 2019) and it works correctly for me. I'm able to trigger and catch an exception from DownloadAsync for a non-existant path. Here's the…

Thanks! We'll work on reproducing the issue using this.

Thanks for the information!

That rate limit with the longer Retry-After should just be a result of making a very large number of API calls for a particular user in a short period of time (as opposed to lock contention). If you're sending thousands of requests very quickly like that, you can run in to it. (It sounds like you would have normally run in…

Can you also share the relevant code showing how you're making the call and attempting to catch the exception so we can try to reproduce that the same way here? Thanks in advance! 

While you can certainly call GetMetadataAsync first, you should be able to directly catch an exception from DownloadAsync in the Dropbox .NET SDK using a catch block. I just gave this a try myself using the latest version of the Dropbox .NET SDK, currently v5.0.0, and it is working for me. I am able to catch the exception…

Thanks for the report! This looks like an issue on our side. We'll look into it, and I'll let you know when I have an update on this.

An "invalid_revision" error from /2/files/restore should mean "The revision is invalid. It may not exist or may point to a deleted file.". In this case, it sounds like it's because the file revision you're using when calling the API is for a version of the file from several months ago, which is no longer be available. File…

It sounds like the Linnworks support team is describing a bug with the Dropbox API. We'll be happy to investigate any issue like that, but there isn't enough information here for us to do so. Please ask Linnworks to report the bug to us directly, including the relevant technical details,…

@"vineet" Здравко is correct, to rename a file via the API, you should use /2/files/move_v2. To rename a file, you should include the full path and file name for the old path/name and new path/name in the 'from_path' and 'to_path' parameters, respectively. You don't need to change any parent path components though. For…

Great, thanks for following up! I'm glad to hear it helps a lot in this case.

@"homedeck" We don't currently have Dropbox product engineers for any particular product, such as Transfer, on the forum here, but thanks for the idea and feedback! I'll float this with them, as well as check in with them regarding the request itself.

Thanks for checking in. We'll make sure we don't leave a gap in coverage. If we do have to extend the migration timeline, we won't cut off the legacy Paper API. We may in fact be updating that timeline soon, but I can't offer specifics or an official update right now. 

Thanks for the report! We're looking into it. I'll follow up here once I have an update on this.