Greg-DB Dropbox Community Moderator

Comments

  • @"jplw" Thanks for the feedback! I'll send it along to the team.
  • Yes, the Dropbox API has a rate limiting system, for both the user and Business endpoints. Note that not all 429s and 503s indicate explicit rate limiting, but in any case that you get a 429 or 503 the best practice is to retry the request, respecting the Retry-After header if given in the response, or using an exponential…
  • API v1 and API v2 offer different interfaces, so you will need to update your code. There's a migration guide here: https://www.dropbox.com/developers/reference/migration-guide
    in API v2 Comment by Greg-DB October 2017
  • If you use the official Dropbox desktop client, it will sync the contents of your Dropbox account to your local filesystem. Note that your local filesystem doesn't use the same path format as the remote Dropbox API though. For example, Dropbox API paths uses '/' as a separator, and not '\'. 1. The Dropbox API isn't really…
  • This error indicates an issue with the app's configuration. The developer of the third party app you're trying to link will need to apply for "production" before more users can connect to it. I recommend you contact the developer of the app asking them to do so.
  • Thanks for the report! Please use the latest SDK release, currently v3.3.4, instead of master for now to avoid this issue.
  • Dropbox webhooks unfortunately don't offer a way to register for notifications for specific folders, but I'll pass this along as a feature request. The best thing to currently do is use the webhook notification functionality that is available, and then call /2/files/list_folder[/continue] when notified to see what did…
  • I just wanted to follow up to update this thread about the current state of this functionality. On iOS 9 and 10, we support Document Picker modes "Import" and "Export", but not modes "Open" and "Move". On iOS 11, we support the new File Provider extension (which is iOS 11 only). Our general recommendation is for people to…
  • The error message is indicating that that's not a valid path value. The Dropbox path format doesn't necessarily match local filesystem path formats. For example, in this case, the path should be like "/NW Region Info Table Documents/0 Special Documents please read first file in this folder/DropboxForSeva.docx". In general,…
  • @"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…
    in API v2 Comment by Greg-DB October 2017
  • 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?