Greg-DB Dropbox Community Moderator

Thanks for the feedback @"srini". We'll review your extension request and follow up with you on your ticket.

Thanks for the post. The expected behavior when uploading via the API to an account when the account is out of space is an error response from the API, that the app can handle as desired (e.g., to surface an error message to the user, and retry later, etc.) For API v1, the error response for this case has a 507 status…

The API doesn't offer a way to programmatically create accounts, but I'll be sure to pass this along as a feature request. (The only exception is for Dropbox Business API apps, which can create accounts in the process of adding members to teams, but that only applies to Business teams.)

Yes, you can use cursors from v1's delta with v2's listFolderContinue and listFolderLongpoll to pick up where you left off.

[Cross-linking for reference: https://stackoverflow.com/questions/44109508/how-to-edit-the-file-in-swiftydropbox?noredirect=1#comment75275980_44109508 ] You can get the profile image via Account.profilePhotoUrl, e.g., as returned by getCurrentAccount.

This can also occur if there are network changes or issues, preventing our servers from reaching yours. That can be transient though, so can you try again? I.e., make a change in a linked account to see if it goes through now. If you're still seeing this, please open a ticket so we can investigate specifically:…

Thanks! It looks like you're using a sample we originally posted on the forum here. Thanks to your post, we found an issue with it that would cause it to fail for very large files, due to the use of smaller int types. We've posted an updated version that uses bigger types here:…

Thanks for the additional feedback!

Yes, we dropped support for iOS 8 support in v3.0.12. We had to do so to support some changes to the authorization flow. There's more information in the release log.

Can you share the code you're using that reproduces this issue? Thanks in advance!

I believe that's referring to things like proxies, firewalls, etc., which may interfere with connections like this. If your users are likely to be in more restrictive environments like this, you may want to not use that in your app, or user different parameters, etc. For reference, the API itself supports a longpoll…

Unlike OAuth 2 access tokens, OAuth 1 access tokens are comprised of two different pieces, a key and a secret. (So, to sign an API call with an OAuth 1 access token, you needed four different pieces: the app key, the app secret, the OAuth 1 access token key, and the OAuth 1 access token secret.) There's an example of the…

Unfortunately there isn't a good solution here. We'll consider it a feature request. Right now, you'd either have to occasionally poll the user endpoints as you mentioned, or for Business apps, monitor /1/team/log/get_events or /2/team_log/get_events.

Yes, you can control how this works by using the "mode" parameter when uploading files. That mode value should be a WriteMode. One of the write modes is "overwrite", though "update" is reccomended, as it's safer. With "overwrite" it's easy to accidentally/unintentionally overwrite new changes you didn't mean to.

[Cross-linking for reference: https://stackoverflow.com/questions/44109508/how-to-edit-the-file-in-swiftydropbox ] Yes, you can edit files of any type, including text files, by uploading the new file data. You can find an example of making an upload call in the documentation for SwiftyDropbox here:…

@"wei-qiang" We'll be happy to help with whatever issues you're having with the Dropbox API. Please feel free to open a new thread with the relevant code and the full error/output you're getting: https://www.dropboxforum.com/t5/forums/postpage/board-id/101000014

Thanks for the feedback!

Yes, you can try making an API call and check if it fails with a 401 invalid access token error. Getting the user's account information is a good call to use for this, since it doesn't have side effects. For example, with the .NET SDK, you can call GetCurrentAccountAsync, and catch/check the AuthError.

1. This is subject to change, so don't rely on this number, but it's generally 1000-2000 files. 2. Yes, even when has_more=false, it's best to store the returned cursor returned by /2/files/list_folder. You can then call /2/files/list_folder/continue later once changes do occur, in order to get information on what (and…

Thanks! I'm glad to hear you got that working. I'll still have engineering investigate this to figure out what's causing that though.

For anyone watching here, there's an update to the linking issue here: https://www.dropboxforum.com/t5/API-support/API-V2-analogue-of-canceFileLoad-and-cancelFileUpload/m-p/222333#M11860

No, unfortunately I don't have any news on this request.

Thanks for following up. I'm glad to hear you got this sorted out.

You can save the task returned by the download/upload call, and then call cancel on it: DBDownloadDataTask *downloadTask = [[client.filesRoutes downloadData:filePath] setResponseBlock:^(DBFILESFileMetadata *metadata, DBFILESDownloadError *downloadError, DBRequestError *error, NSData *fileData) { // ... }]; // ...…

You appear to be trying to access "www.dropboxapi.com", but that isn't a supported domain. The Dropbox website is at www.dropbox.com (no 'api'), and the API is available, depending on functionality, across: (no 'www') - api.dropboxapi.com - content.dropboxapi.com - notify.dropboxapi.com Each of the endpoints document which…

Thanks! It appears these two files only differ by two seemingly random bytes. If you can print the full metadata returned by the upload call, and a hash value of the returned contents of mem right before the corrupted upload, that would be helpful. Also, since it seems like this happens randomly, if you could also include…

Thanks for the report! We'll be happy to look into this, but we could use some more information to help us reproduce this. Can you please share: - a sample original file (before being corrupted) - the output of some additional logging showing the correct contents in the mem object before upload (e.g., a hash) - the output…

Thanks for the feedback! Please feel free to report any other issues as you did with the first and we'll be happy to look into them. (You can post here, or you can open a ticket if you'd prefer to share privately: https://www.dropbox.com/developers/contact )

The SwiftyDropbox SDK should already automatically store the linked account for you. You can retrieve it using "authorizedClient" as shown in the example here: https://github.com/dropbox/PhotoWatch/blob/48df3b99b47f4a883703f7a4cd9512eb2a5c0cb2/PhotoWatch/ViewController.swift#L22 Is this not working for you?

For a server-side integration, such as when using PHP, it would be inefficient to upload to your server first and then to the Dropbox API. You can avoid this by writing the Dropbox API functionality to run client-side instead. For example, you can use the API v2 JavaScript SDK: https://github.com/dropbox/dropbox-sdk-js…