Greg-DB Dropbox Community Moderator

@"jdbrown" It looks like this may be an issue with Chrome. With what version(s) of Chrome are you seeing this issue? I was able to reproduce the issue with Chrome 61.0.3163.100, but it works again for me in Chrome 62.0.3202.75, so it looks like it may already be fixed in new versions.

No, unfortunately file requests don't accept entire folder uploads, only files.

It sounds like you're calling startOAuth2Authentication every time. You should only call that (or let the user trigger it) when necessary. You can see how the example app checks if it already has a token here. The startOAuth2Authentication method can throw IllegalStateException, so you can catch that normally.

The Dropbox API now offers the ability to get thumbnails in batches: https://www.dropbox.com/developers/documentation/http/documentation#files-get_thumbnail_batch If you're using an official SDK, there will also be a corresponding method for this endpoint.

The Dropbox API now offers the ability to get thumbnails in batches. In the Objective-C SDK, that's available as: https://dropbox.github.io/dropbox-sdk-obj-c/api-docs/latest/Classes/DBFILESUserAuthRoutes.html#/c:objc(cs)DBFILESUserAuthRoutes(im)getThumbnailBatch:

The Dropbox API now offers the ability to get thumbnails in batches. In the .NET SDK, that's available as: https://dropbox.github.io/dropbox-sdk-dotnet/html/M_Dropbox_Api_Files_Routes_FilesUserRoutes_GetThumbnailBatchAsync_1.htm

The Dropbox API now offers the ability to get thumbnails in batches. In the .NET SDK, that's available as: https://dropbox.github.io/dropbox-sdk-dotnet/html/M_Dropbox_Api_Files_Routes_FilesUserRoutes_GetThumbnailBatchAsync_1.htm

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

Whenever debugging issues like this (or to retrieve the result, e.g., the file metadata, etc., even in the case of success) be sure to read the response body. It will contain more information, such as a specific error message. Based on your description though, it looks like the issue is that you're using a Business app…

Hi Florian, thanks for the report! It looks like we are having some trouble with the analytics reporting right now. We're looking into it.

@"Qbert" There's an example of downloading a file here. Or, you can call download to get a DbxDownloader and call DbxDownloader.getInputStream on it to get an input stream similar to how the v1 getFileStream method worked. To get the FileMetadata for a particular file, you can call getMetadata. The use of…

The API doesn't offer the ability to download with a wildcard like this. You'll need to call once per file with the exact file path. You can get the file names using files_list_folder and files_list_folder_continue.

@"Marcos_Soares" Rich is correct, your code uses API v1, which is retired, so the call will fail. You should migrate to API v2 instead. For example, the equivalent of /1/files_put is /2/files/upload. By the way, if you need more time to migrate your app to API v2, we can offer an extension for access to API v1. To request…

The Dropbox Java SDK you're using (v1.7.6) is old and is using the now retired API v1. Calling API v1 will return a 400 error since it is now disabled. You should instead use the latest version of the Dropbox Java SDK (currently v3.0.5), which uses API v2.

The SDK has a copy of the API specification and can tell when the supplied value isn't valid without making a call to the server (and thus without going through the API error callback). You'll need to prevent your app from using invalid values like this in the first place. E.g., only use safe values returned by the API,…

An incorrect_offset error indicates that you're trying to upload to an offset that doesn't match what the server last saw for this upload session. For instance, this can happen if previous request was received and processed successfully but the client did not receive the response, e.g. due to a network error. The…

You're not doing anything wrong. Dropbox is case-insensitive, and attempts to be case-preserving, but sometimes you won't see the original expected case. You should use pathLower when performing operations, as that's the canonicalized version of the path. You should use pathDisplay for display purposes, where the case will…

A path/conflict/folder error indicates that the upload failed because there is a folder in the way: https://dropbox.github.io/dropbox-sdk-java/api-docs/v3.0.x/com/dropbox/core/v2/files/WriteConflictError.html#FOLDER Note that if you're trying to upload a file into that folder, you'll need to specify the full desired path,…

You probably need to use open(xls, 'rb') instead of open(xls, 'r'). (Note the 'b' in the mode.) Try that out and let me know if it doesn't help.

The API was designed with the intention that each user would link their own Dropbox account, in order to interact with their own files. However, it is technically possible to connect to just one account, as you've done, but we don't recommend doing so, for various technical and security reasons, like you mentioned. Anyway,…

Thanks! I'm glad to hear you were able to track that down. @"Drageniix" If you're still seeing this, can you try that as well?

Thanks for following up. I'm glad to hear you were able to get this working by running it outside of the app lifecycle methods. This is useful information though so we'll see if we can track down why that doesn't work. Apologies for the trouble!

Thanks for the post! There isn't a way to force that, but I'll pass this along as a feature request for the old/filename in URL version, though I can't make any promises as to if/when then would be done. For reference, the filename is included in the 'Content-Disposition` header, which the HTTP client should be using, but…

Thanks for the information! Can you elaborate on what exactly you did to clear the Keychain to get that working though? (This is supposed to be done automatically for you.) You can see where this is done in the SDK in the following stack of DropboxClientsManager.unlinkClients -> DropboxOAuthManager.clearStoredAccessTokens…

API v2 does offer a different interface than API v1, so you will need to update your SDK and code. For Android, we recommend using the official Dropbox API v2 Java SDK: https://github.com/dropbox/dropbox-sdk-java There's an example Android app here: https://github.com/dropbox/dropbox-sdk-java/tree/master/examples/android…

@"Qbert" If you want to use the jars directly, you can find them in the tar/zip downloads for each release: https://github.com/dropbox/dropbox-sdk-java/releases That includes the required dependencies, i.e., just the 'dropbox' and 'jackson' jars, which is all you need typically. (It doesn't include optional dependencies…

Thanks for the feedback Markus!

If you don't need to link more than 50 users, you don't need to get your app switched to production, and can just keep it in development mode. It is technically possible to link up to 500 while still in development mode too, but note that there's a time limit on that. You can find more information here:…

@"thorty" Using the DbxWebAuth flow you have is a valid way to get another access token, and that shouldn't revoke any previous tokens Can you elaborate on the issue you're having with the previous token? E.g., please share the code and full output. Make sure you're not mixing up the "authorization code" and "access…

Thanks! I'll ask the team to improve the documentation around this.