Greg-DB Dropbox Community Moderator

SwiftyDropbox now supports Swift 3, as of version 4.0.0. Please grab the latest version 4.0.2, and let us know if you run in to any issues.

Thanks for the report Mark! We are working on updating SwiftyDropbox for Swift 3 to take care of this.

Hi Rob, can you share your Podfile and version number of CocoaPods? Thanks in advance! 

That's correct. The Android SDK doesn't do it for you, but the iOS SDK does automatically store access tokens in the keychain for you, so you don't have to. 

Also, in response to your edit, you don't need to call unlinkClients each time, though that will clear out authorizedClient if that's what you want to do. You can re-use the tokens the SDK stores for you without having the user go through the app authorization flow each time (authorizeFromController).

Hi Robert, that assertion is actually easy enough to hit if you call authorizeFromController more than once (if you do link an account the first time). The DropboxClientsManager class is meant as a convenience for the standard single account case, so you can use the following to check if you're already linked: if…

This should be fixed now. Please let me know if you're still seeing any issues.

Thanks for the report! This is a known issue that should be fixed soon.

The standard Dropbox Saver button itself doesn't offer customization options. If you want to use a custom button though, you build your own button and then hook it up to the Saver functionality using JavaScript as shown here: https://www.dropbox.com/developers/saver#triggering

Thanks! I'm sending this along to the team as a feature request.

Thanks for the feedback, Kiko. I can't promise if/when we might write an example like that, but I'm sending it along to the team. For reference, instructions for running the Android sample can be found here: https://github.com/dropbox/dropbox-sdk-java/tree/master/examples/android The app authorization flow specifically is…

I'm not too familiar with PowerShell, but it looks like you may be able to get the response body using the -OutFile option on Invoke-RestMethod. Also, for reference, based on your code, you're using API v1, which is now deprecated. We recommend migrating to API v2 when you can. For example, the equivalent…

Thanks for following up Vasili. What you shared is just the status line of the response though. Can you retrieve and share the body of the response as well? Based on your description of the problem, it's likely related to the encoding you're using for these characters. Please also share the code you're using to make the…

Vasili, what's the content of the response body? It should contain a specific error message indicating the issue.

What specifically isn't working as expected? Are you getting an error? There's a sample here that may be helpful: https://stackoverflow.com/documentation/dropbox-api/409/uploading-a-file/1357/uploading-a-file-with-every-error-case-handled-using-the-swiftydropbox-library#t=201609081416309785993

Hi Vishal, no, the API doesn't expose a way to upgrade an account's plan programmatically, but I'll be sure to pass this along as a feature request. 

No, unfortunately this information isn't available via the API. I'll pass this along as a feature request though.

[Cross-linking for reference: https://stackoverflow.com/questions/39344740/dropbox-java-api-upload-file ] It looks like you've already found the methods for uploading and creating shared links. Is your code not working? If not, what error are you getting?

That's correct, for API v2 /files/list_revisions, the max limit is currently 100. We'll make a note to add this to the documentation. There isn't currently a way to request more than that, but we'll consider that a feature request.

What happens when you run this code? Do you get an exception?

It sounds like you registered your app for the "app folder" permission. You'll need to register a new one for the "full Dropbox" permission to access the Public folder: https://www.dropbox.com/developers/apps/create

Yes, you need an access token to upload to an account via the API. If you just need to upload to your own account, you can get an access token for your app-user pair by using the "Generate" button on your app's page on the App Console. Otherwise, to get an access token for any arbitrary account, you'll need to use the…

Hi Eytan, you can use the Dropbox API to programmatically upload to the Public folder just like any other folder. Using the API v2 .NET SDK, for example, you can use the UploadAsync method to upload into the Public folder, e.g., by supplying a path like "/Public/uploadedfile.ext".

Hi Eugene, yes, you can still construct an API v2 call for a "content-download" endpoint like this using just a URL. You can find information on this in the formats section of the documentation. For example, for the /2/files/download endpoint, instead of the typical way as shown in the example: curl -X POST…

We don't currently document or guarantee a maximum possible page size for /list_folder, but if I recall correctly, you will generally see 1-2 thousand entries per page. I've sent this along as requests for a documented maximum, as well as the ability to set custom page sizes.

Steve is correct, this isn't available in API v2, but I'll be sure to pass this along as a feature request. 

Thanks for writing this up. Unfortunately, API v2 doesn't offer a way to specifically request particular Content-Type like this. I'll send this along as a feature request, but I can't promise that it will be implemented. Apologies I don't have a better answer for you!

For reference, the known issue with lowered path_display values for deleted files in particular should be fixed now.

Thanks for following up with that Todd. That behavior is expected. Dropbox itself is case-insensitive, with attempts to be case-preserving. However, due to various specifics, the API can't always return the expected case for every path component. So, for any file or folder metadata, the filename/last path component should…

Hi Todd, this is a good place to report bugs like this. Are you seeing this only for deleted metadata, or for all metadata? There's a known issue for this for deleted metadata, but if you're also seeing this for non-deleted metadata, please share a sample so we can look into it. Thanks in advance!