Greg-DB Dropbox Community Moderator

Apologies, no ETA on the fix right now.

[Thanks for reposting. The API development forum is the right one for anything API related. The "Bugs & Troubleshooting" forum is more about the Dropbox product itself. I've deleted your other post so we can consolidate here.] Anyway, the Dropbox iOS Core SDK doesn't use NSURLSession. It's a wrapper around the HTTP…

Thanks! It looks like the issue is that you have an extra comma character after each piece of your tokens. I.e., your oauth_consumer_key has a value like "xxxxxxxxxxxxxxxx," instead of "xxxxxxxxxxxxxxxx". We'll look into fixing our parsing so that we don't error out on that, but to get it working on your side, just remove…

Thanks! In that case, can you make this small edit to the Ruby SDK to enable some additional debugging output? Just add this third line (with set_debug_output) after http is defined in the self.do_http def in the Dropbox module in dropbox_sdk.rb: def self.do_http(uri, request) # :nodoc: http = Net::HTTP.new(uri.host,…

[Cross-linking for reference: https://stackoverflow.com/questions/32809360/dropbox-core-api-500-internal-server-error-on-a-remote-server-only-works-fine ] A few questions to help track this down: - Does this occur for every account_info call you make for that user on the AWS server? - Are the app key/secret and access…

Thanks! Yes, unfortunately we don't have good documentation around this for the iOS Core SDK. (If you're just starting out and can use Swift though, you may want to use the Dropbox SwiftyDropbox SDK instead, which has better documentation and more explicit error handling.) Anyway, it sounds like you've already handled…

So are you using the SDK or calling the API directly?

Sorry, I should have been clearer, I was referring to the Dropbox SDK you're using (if any). For example, are you using the Dropbox iOS Core SDK for API v1, or the newer SwiftyDropbox SDK for API v2?

What API/SDK are you using in particular?

It looks like you also have an old version of the SDK added: dropbox-core-sdk-1.7.7.jar Can you remove that and try again? Also, try the "account-info" example that's included with the SDK.

Apologies, the documentation is wrong. We'll get that fixed up. The header should be "Dropbox-API-Select-User". Please try that and let us know if you still see any issues.

It looks like this is a bug on our side. We're looking into it.

Richard's correct, Dropbox API apps should not handle the user's credentials, but should use the OAuth flow instead. Note that this only needs to be done once per user. Once your app has an access token for a user, it can store and re-use the access token for future API calls for that user without further manual user…

Thanks for writing this up! I'm passing this along as a feature request.

Thanks for the clarification! I'm sending this along to the right people as feedback.

The Dropbox Chooser should automatically use the language set for the user in the user's account settings without any configuration from the app. This seems to be working for me: Is this not working for you?

For large files, you should use chunked uploading: https://www.dropboxstatic.com/static/developers/dropbox-android-sdk-1.6.3-docs/com/dropbox/client2/DropboxAPI.ChunkedUploader.html

You can use GetThumbnailAsync to get thumbnails.

You can use ListFolderAsync to get file/folder listings, and DownloadAsync to download files. The tutorial has samples of both.

The /sharing/remove_folder_member documentation says: "dropbox_id String Dropbox account, team member, or group ID of member to add." So, you have a few choices of what kind of ID you can supply. For example, you can get a Dropbox account ID from /users/get_current_account (for the linked user), or of members of a shared…

The serialization methods are now public in version 3.1.0.

Thanks for the writeup Aibek! I'm sending these along as feature requests, though I can't make any promises about if or when they'd be implemented. One note, it doesn't sounds like you necessarily are, but just to be sure/for anyone else reading, you definitely shouldn't rely on email address as an account identifier in…

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

Thanks for the report Dennis! This is a known issue that the team is working on.

Hi Grant, thanks for the report. I can't seem to reproduce this here though. About what percent of your API calls are failing? For reference, I just tried this simplified code, using v2.2.0 of the SDK: import dropbox ACCESS_TOKEN = '...' client = dropbox.client.DropboxClient(ACCESS_TOKEN) for i in range(100): print(i) #…

Thanks! That's likely the cause here then. The media information can take some time to generate, before which the entries can't be returned for these cursors. We're always working to keep these delays to a minimum, but they can vary. Unfortunately I don't have a perfect solution to offer here, but you may want to just…

Production status wouldn't help here, as that just enables more users to connect to your app. Are you using include_media_info=true when you originally get these cursors though?

Thanks for the feedback! We don't currently have documentation for this, but I'll be sure to pass this along as a request for some.

Thanks for the additional information Quentin! I believe that is in fact the issue, in that the Dropbox document picker doesn't currently support folders/packages, so sending a zip file would be better. I'm sending this along as a feature request though.

I don't think there should be anything special about using UIDocumentPickerModeExportToService with Dropbox in particular. Can you share some sample code and steps to reproduce the issue so we can look into it? Thanks in advance!