Greg-DB Dropbox Community Moderator

Hi Olaf, for downloading, you generally just need a simple call to the files_download method. There's a sample here: https://stackoverflow.com/documentation/dropbox-api/408/downloading-a-file/1350/downloading-a-file-using-the-dropbox-python-library#t=201607262010533665443 Are you running into issues downloading large files?

Thanks! That URL indicates that your Chooser is being used from the domain dev.leadalead.com. However, the app for key wn7rjp4bsjx6z4l (with name "Ydncrm") isn't registered for that domain. Please sign in to the account that owns that app and add dev.leadalead.com as a "Chooser/Saver domain" using the App Console. (Or, if…

Hi Stephanie, can you share the URL of the Chooser window giving you this error? Thanks in advance! 

Hi Jinia, thanks for your interest! You can learn more about the reseller program at the link Rich provided.

This is a general problem with using OAuth in client-side applications, since client-side apps like this can't keep secrets. OAuth 2 addresses this with the "token" or "implicit" flow. When using the token flow (as opposed to the "code" flow), the app doesn't need the app secret to get an access token for the user. You can…

The closed error from /files/upload_session/append_v2 should indicate that the upload session identified by the session_id is already closed. Can you share the request/response for the call to /files/upload_session/start? (Just be sure to redact the access token and file content.)

That's correct. The rev value uniquely identifies the file in the Dropbox, including path, so you don't need to add a path too.

Yes, API v2 offers structured exceptions, so you can detect specific scenarios like this. The documentation for createFolder covers all of the types of exceptions it can throw. For example, to detect this particular error case: try { FolderMetadata folder = client.files().createFolder("/test_java_createFolder");…

Hi Robert, just trying to create the folder and catching the exception is a fine way to handle this. It's as efficient as possible too, since it just requires the one API call. If you do want to check ahead of time, you can use getMetadata. That will throw an exception if the folder doesn't exist though anyway, which you…

I can't seem to reproduce that error. How are you building/running this? Make sure the Dropbox library is added properly: https://www.dropbox.com/developers/documentation/java#install

The Sync SDK did offer offline caching and queuing, but the API v2 SDKs do not. That being the case, if you need this functionality, you'll have to implement it in your application's code. E.g., if you get such an exception when attempting the upload, save the file to upload in a queue, and have your app try again when it…

There are standard timeouts, but you can also set custom ones using StandardHttpRequestor.Config.Builder.

The API v2 Java SDK doesn't handle storing the access token for you (like the Sync SDK did), so this is under your control. If you want to "unlink" the user, you can just throw away the access token you have stored for the user. You can additionally revoke the token using the tokenRevoke method.

The API v2 SDKs don't provide caching layers for you like the Sync SDKs did, but if you are caching file content locally like that, the rev value you mentioned can be used to keep track of changes. That is, when you store a copy of a file locally, store the rev value for that copy as well. When you see the remote rev value…

Thanks for the feedback Ashley! We don't have a system for developers to set up test accounts for themselves for the Dropbox Business API like that right now, but I'll be sure to pass this along as a feature request. I don't know if or when that would be implemented though. Apologies I don't have more useful information to…

It looks like you're using the iOS Core SDK. No, the DBMetadata object in that doesn't offer anything quite like that. You can pull the file extension off of the file name though and compare that to a list of image file extensions you're interested in though. (Also, I should note that the iOS Core SDK uses API v1, which is…

Here's a simple example that shows how to use that method: try { SharedLinkMetadata sharedLinkMetadata = client.sharing().createSharedLinkWithSettings("/test.txt"); System.out.println(sharedLinkMetadata.getUrl()); } catch (CreateSharedLinkWithSettingsErrorException ex) { System.out.println(ex); } catch (DbxException ex) {…

[Cross-linking for reference: https://stackoverflow.com/questions/36861838/is-it-possible-to-get-the-share-link-via-dropbox-api-call-for-a-file-which-has-b ] You can use the Dropbox API to get a shared link for a file you've uploaded. It isn't included with the file metadata itself, so you just need to make an additional…

Hi Jeff, a few things first: - You're calling the beta /2-beta-2/ route. You should update to the stable /2/ route. - I can't see the request body view in the second screenshot, can you share one that shows the raw body being sent up? 

Hi Shivkanth, that's not currently possible, but I'm passing this along as a feature request.

Thanks Jordan! That actually works fine for me though. I get redirected back to the test app and get the "Success! User is logged into Dropbox with token: ..." message on a device running iOS 9 with the official Dropbox app installed. Is this happening on multiple devices/simulators for you? You may also want to try…

Thanks for the additional information. In your original post though, you said "the app just quits with out throwing any errors after the redirect back to the app", however in your last reply you said it "still fails to redirect". Can you clarify what redirect does or doesn't occur, and when the app quits exactly? In any…

What version of iOS are you running? The only thing that looks potentially wrong is that you're using the older version of the openURL method. There's a note in the tutorial here about that: https://www.dropbox.com/developers/documentation/swift#tutorial You can use this version for 9.0+: func application(app:…

For reference, we've now reverted the behavior change, so the double slash version should work again. We do recommend only using a single slash though.

Apologies for the inconvenience Pankaj! We of course never want to break apps, and we email and post on the blog whenever we are planning a breaking change or deprecation. This change in validation wasn't intended to be a breaking change though, so there wasn't any outreach. 

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

That's very helpful, thanks Martin! We're looking into it.

Hi Martin, can you share a screenshot of that so I can make sure I understand the issue and get it to the right people? Thanks in advance! 

This is fixed now. Please let us know if you're still seeing any issues.

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