Greg-DB Dropbox Community Moderator

I'm not sure there are any drawbacks, but that's not really the intended way of using it, so I wouldn't recommend doing so.

I don't know off hand what the behavior in that case would be, but if you're using a personal account, you shouldn't use a team client to begin with.

There isn't a "current" user, so no user will be set. So, if you set null, it will just cause any user calls to fail.

In your sample code, the file isn't saved anywhere. The data is just available via the download object. In my sample, the file is saved to the path "Test", but if you use that you should of course change that as desired.

Actually, for reference, you can track progress if you use GetContentAsStreamAsync. E.g., you can do something like: var response = await client.Files.DownloadAsync(path); ulong fileSize = response.Response.Size; const int bufferSize = 1024 * 1024; var buffer = new byte[bufferSize];…

The Dropbox.NET SDK doesn't currently offer a way to get the progress of a download, but I'll be sure to pass this along as a feature request. It also doesn't offer a way to download folders in bulk, so you'll need to iterate through to download each desired file.

This should be fixed now in v2.1.2. Please update and let me know if you're still seeing any issues.

Thanks for the report Phil! We're looking into it.

This did change a bit over the versions. Are you using the latest version of the SDK? If not, please pod update and try again. 

I see, thanks for clarifying. We do have a general import you can use as shown in the readme: #import <ObjectiveDropboxOfficial/ObjectiveDropboxOfficial.h>

Glad to hear that's working now. That import shouldn't really be necessary though. What version of the SDK do you have installed? What other imports do you have?

That would also be a path conflict error. The conflict error itself just means that something is already at the path. You can then check that DBFILESWriteConflictError to see if it was a file or folder, e.g. to expand on my last example: [[client.filesRoutes createFolder:@"/testfolder"] response:^(DBFILESFolderMetadata…

In this case, you'd get a DBFILESCreateFolderError in your cfError variable, containing a "conflict" DBFILESWriteError in the path field. Here's an example of how you'd detect the different error cases, picking out the conflict error: [[client.filesRoutes createFolder:@"/testfolder"] response:^(DBFILESFolderMetadata…

This is now available via /list_file_members: https://www.dropbox.com/developers/documentation/http/documentation#sharing-list_file_members https://www.dropbox.com/developers/documentation/http/documentation#sharing-list_file_members-continue…

No, this isn't possible with the Dropbox API, but I'll be sure to pass this along as a feature request.

You're using Dropbox API v1, a.k.a. the Core API. API v1 supports both OAuth 1 and OAuth 2. You seem to be mixing OAuth 1 and OAuth 2, but you're only supposed to use one or the other for any particular API call. I.e., the "access_token" parameter and the "Authorization" header are ways to supply an OAuth 2 access token.…

Hi Eric, you can use instanceof to determine if a given Metadata is an instance of FileMetadata, FolderMetadata, or DeletedMetadata and then cast it accordingly, e.g., as shown here:…

I believe either way is safe as long as you have that isAuthError check. The asAuthError call just gives you the object as DBRequestAuthError instead of DBRequestHttpError, but it doesn't seem to make a difference in this case.

Hi Robert, it sounds like you're looking for the structuredAuthError property on DBRequestAuthError. That will give you the DBAUTHAuthError, on which you can call isInvalidAccessToken etc. E.g.: if (authError.structuredAuthError.isInvalidAccessToken) { NSLog(@"Invalid acess token."); } Hope this helps! 

I'm not aware of any immediate plans, but I'll send this along as a feature request.

I'm not seeing this in Safari. Can you share some code to reproduce the issue? Also, please let us know what version of Safari you're using. Also, if you are seeing it in Safari, doe the answer at http://stackoverflow.com/a/34168434/1305693 help? Thanks in advance! 

Hi Siddharth, I believe this is an issue where we may not be trusting one of the Certificate Authorities on your certificate. We're checking if we can fix this on our side, but I can't say if/when that would be. Some workarounds for now that may help to get this working from your side: - use http:// for your webhook URI…

Hi George, yes, recent changes may not immediately be reflected in search results due to a short delay in indexing. We'll get that clarified in the documentation. For this kind of application, you may be better suited by directly checking with files_get_metadata though. I.e., you can check for 'printmessage=1'…

What exactly happens when "AVAsset does not get created properly"? Do you get an error? I suspect the issue is that a shared link doesn't directly point to the file content, but rather an HTML preview. You can modify these links for direct content access though, as shown here: https://www.dropbox.com/help/201 Note that…

API v2 and SwiftyDropbox don't currently have an equivalent of loadStreamableURLForFile, but I'll be sure to pass this along as a feature request.

The official Objective-C SDK for API v2 has been released here: https://github.com/dropbox/dropbox-sdk-obj-c

Raheel, the Datastore API will be disabled at the end of April, so any datastores syncing functionality, including in the Sync/Datastores SDK, will stop working then.

That's correct, we haven't announced any timeline for deprecating the Core API, so while we recommend moving off of the Sync SDK, it should continue working.

Hi Joe, we don't currently have an official Objective-C SDK, tutorial, or documentation for API v2, but it is something we're planning. I'll be sure to pass this along as feedback as well. Also, note that both API v1 and v2 are currently supported. While API v2 is preferred, API v1 a.k.a. the Core API hasn't been…

This should be fixed as of version 2.0-beta-6 of the SDK, where we exposed the ability to configure socket read timeouts for StandardHttpRequestor. You can find a sample of using longpoll here: https://github.com/dropbox/dropbox-sdk-java/blob/master/examples/longpoll/src/com/dropbox/core/examples/longpoll/Main.java