Greg-DB Dropbox Community Moderator

It sounds like the Dropbox part of this is working, and you're having trouble with the UI side of this. That's outside the scope of Dropbox API support, so I'm afraid I can't be of any help with that.

Here's a sample of uploading using upload sessions: private async Task ChunkUpload(String path, FileStream stream, int chunkSize) { int numChunks = (int)Math.Ceiling((double)stream.Length / chunkSize); byte[] buffer = new byte[chunkSize]; string sessionId = null; for (var idx = 0; idx < numChunks; idx++) { var byteRead =…

The .NET SDK doesn't offer native progress listeners, but I'll be sure to pass this along as a feature request. You can however track download progress using GetContentAsStreamAsync. E.g., you can do something like: var response = await client.Files.DownloadAsync(path); ulong fileSize = response.Response.Size; const int…

The recommended installation method for the official Dropbox .NET SDK is NuGet, but if you don't want to use that, the SDK itself is available for download here: https://github.com/dropbox/dropbox-sdk-dotnet

For what it's worth, I just tried this using that Podfile, as well as the same version of CocoaPods and Xcode you cited and I couldn't reproduce the errors you're getting.

[Cross-linking for reference: https://stackoverflow.com/questions/37857629/swiftydropbox-errors-after-installation ] This may not be specific to SwiftyDropbox. There are some existing posts that may be helpful though: https://stackoverflow.com/questions/24622650/xcode-6-beta-3-invalid-virtual-filesystem-overlay-file…

I think the issue is with your writeMode.AsOverwrite. You can instead do this: commitInfo = new Dropbox.Api.Files.CommitInfo(path, Dropbox.Api.Files.WriteMode.Overwrite.Instance, false, null, false);

API v1 is the older version of the Dropbox API. API v2 is recommended, but API v1 is still usable. For reference, the iOS Core SDK uses API v1, and SwiftyDropbox uses API v2. The iOS Core SDK unfortunately doesn't implement the API v1 /metadata/link endpoint, but you can implement it separately if you want.

Dropbox API v2 does have endpoints for getting shared link metadata and files, but unfortunately they don't currently offer the file listing for links that point to folders. So, if you knew the names of the files you want to download in the folder, that would work, but you can't list the names using that. The v1 version of…

MapQuest, I'm not sure I understand your question. In any case, this thread was about a specific issue with the Dropbox API that has since been resolved. If you have a question about the Dropbox API, please feel free to open a new thread with the details:…

The /files (POST) endpoint should be working again now. Please let me know if you're still seeing any issues.

[Cross-linking for reference: https://stackoverflow.com/questions/36264051/dropbox-rest-api-404-error-when-uploading-file ] Hi Daniel, thanks for the report! That's correct, this seems to be the same issue as reported in that other thread. The team is investigating, but I don't have a timeline for a fix to offer right now.

We generally prefer using TestFlight to receive test copies of apps like this. When you click the "iOS" platform button on the "Request production status" page you'll be shown more specific information.

The /files (POST) endpoint should be working again now. Please let me know if you're still seeing any issues.

Hi Deon, the first error is just about how you're using curl, so I can't offer insight on that. The second error sounds like it's due to a recent issue that we're looking into. (You can find more information here.) We do highly recommend using /files_put instead though, if possible.

I haven't tried it myself, but it looks like you may need to use -ContentType ''.

The message says that the API call expects a missing or empty Content-Type, and that you provided 'application/x-www-form-urlencoded', not that you should provide it. You should instead make sure you don't send a Content-Type header at all, or if you do, make sure it's empty.

That's just the status. Check the body of the response for more information.

What does the body of the 400 response show? It should be an error indicating the issue.

[Cross-linking for reference: https://github.com/dropbox/dropbox-sdk-java/issues/58 ]

The /files (POST) endpoint should be working again now. Please let me know if you're still seeing any issues.

Thanks for the additional information, it's very helpful. The /1/files (POST) endpoint is an old upload method on the Core API, a.k.a. API v1. That endpoint is technically supported, and it looks like its behavior did change, which we're looking in to. However, we do strongly recommend using /1/files_put instead, as it's…

Thanks for the additional report Freddie. Can you share the relevant code? That would help us reproduce the track down the issue.

Can you share some sample code to reproduce the issue? Thanks in advance! 

That path parameter isn't a filter, exactly. Rather, the documentation also says: "If a non-empty path is given, returns a list of all shared links that allow access to the given path - direct links to the given path and links to parent folders of the given path. " That means that calling for /myfolder won't list links for…

Hi Eric, development and production mode are the same as far as webhooks are concerned. Anyway, we do automatically email you when a webhook URI is disabled. The system will email the email address registered on the Dropbox account that owns the app though, so make sure that address is up to date, and maybe check your spam…

If you want to create a shared link for a file and you know the id for the file, you can just use that, as opposed to trying to combine path and id. That is, if "id:h8f3g764f73gf7fg" is the id for a file at /myfolder/myfile that you want a shared link for, you can just use the id only: curl -X POST…

Hi Tharan, if you want to get a link to the file content, you can use the /2/files/get_temporary_link endpoint: https://www.dropbox.com/developers/documentation/http/documentation#files-get_temporary_link Or, if you want to get thumbnails for the images, instead of the full image file, you can use /2/files/get_thumbnail:…

Hi Mark, the exception and unsupported_extension error you shared is actually for the files.getThumbnail method, not files.download. It looks like you're accidentally calling getThumbnail. The files.download method works for .rtf files.

This isn't currently available in the Dropbox API, but I'll be sure to pass this along as a feature request!