Greg-DB Dropbox Community Moderator

[Cross-linking for reference: https://stackoverflow.com/questions/34415945/how-to-get-actual-versionrevision-number-of-file-containing-multiple-versions ]

The 500 for invalid IDs should be fixed now.

No update on the 500 error issue. I'll follow up here when this is resolved. The other issue, with the slightly changed file ID, behaves this way because of how these IDs are encoded. That is, a small portion of the ID (at the end) is irrelevant, so changing it doesn't affect the operation.

Thanks for the report! We're looking into these issues.

Hi Aldo, file IDs aren't really exposed to users anywhere. They're intended as an aid for developers in the implementation of apps.

Changing the contents of a file doesn't change the file ID, but does changes change the rev. That is, a file ID identifies a file, even across revisions, but the rev identifies a specific revision of a file. Likewise, if you delete and restore a file, or move a file, the ID won't change, but the rev will. If you make a…

The API v2 Java SDK downloadBuilder doesn't currently support file IDs, so you'll have to a path. I'll be sure to pass this along as a request though.

This sounds like it should be possible. Specifically: - There isn't a special kind of account for this, but a normal account should work. You can register an account here: https://www.dropbox.com/register - Yes, you can use the new API v2 shared folder endpoints to share folders and invite users:…

Richard's correct, the user needs to be involved at least once to authorize the app to access their account. There's an OAuth guide that outlines this here: https://www.dropbox.com/developers/reference/oauth-guide The only exception is if you only intend to have your app connect to your own, single account. That is…

Thanks! That also works for me, so it is likely an account-specific issue. We'll follow up here once we have an update for you.

Thanks! That's helpful. We'll look into that error. For reference, yes, both of these versions work for me: curl -X POST https://api.dropboxapi.com/2/sharing/list_shared_links \ --header "Authorization: Bearer <ACCESS_TOKEN>" curl -X POST https://api.dropboxapi.com/2/sharing/list_shared_links \ --header "Authorization:…

Thanks for the report! I can reproduce the unexpected error when supplying an empty path, which we'll look into, but I can't reproduce the 500 when not supplying a path. Can you share your code and output? The response headers would be useful in particular. Thanks in advance! 

You need to URI encode the path in the URL. For example, to download a portion of a file at "/tést.txt" using curl: curl "https://content.dropboxapi.com/1/files/auto/t%C3%A9st.txt" \ -H "Authorization: Bearer <ACCESS_TOKEN>" \ -H "Range:bytes=0-3"

This is still planned, but I don't have a timeline to share right now unfortunately. As a workaround, you can use /files (GET) on API v1 with Range Retrieval Requests, with the same OAuth 2 auth.

Thanks for the feedback, Norbert! I'm sending it along.

API v2 doesn't currently support Range Retrieval Requests, but we are planning on adding it in the future.

No update on this right now. Apologies I don't have better news!

Hi David, I don't have an update on this unfortunately. Also, we can't provide any absolute guarantee of an app's compliance based on this hypothetical description, so you should be sure to review all the guidelines and terms before developing an app: https://www.dropbox.com/developers/reference/tos…

Thanks! I can't make any promises one way or another, but I'm sending this along to the team as a feature request.

Michael, it sounds like you're seeing an error when trying to authorize your app on an account? This thread was about an error when using the /files/move endpoint in particular. Please open a new thread or open an API ticket with the details of the issue you're seeing so we can look into it.

Apologies for not followup up here! Yes, this should be resolved now.

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?