Greg-DB Dropbox Community Moderator

[Cross-linking for reference: https://stackoverflow.com/questions/42690512/download-file-not-working-with-dropbox-api ] Thanks for following up with the additional information. If you're seeing the file metadata as you describe, that means the API call itself worked. When using that getFile method like this, the file data…

Hi Dave, it sounds like you're using an old version of the API v1 Python SDK, with an outdated certificate file. We reached out to developers using old SDKs like this last year to warn of this change, but it sounds like that email didn't make it to you unfortunately. In any case, you should be able to fix this by just…

By new access token, I mean you should retrieve another. This won't be any different that the old one, except that the old one is now revoked. It is important that the old one was revoked because you posted it publicly, meaning any person could have taken it and accessed your account. Once you have a working access token…

Are you running the version with "<ACCESS_TOKEN>", or did you just redact your access token like that for posting the error here? That's not a valid access token, and since you revoked the app, you'll need to retrieve a new access token to run your code. Make sure you use your access token exactly as provided, that is,…

Hi Ed, thanks for the post. That's correct, the Dropbox API doesn't offer delta uploading like that. I'll pass this along as a feature request. Apologies I don't have better news!

Thanks! We'll look into it.

Thanks for the report! Can you share the relevant code snippet, as well as any error or output you might be getting in the console? Thanks in advance!

To revoke an app, click the 'x' at the far right of the app's row.

I redacted your access token from your post, but you should revoke it now since it was publicly posted. You can do so by revoking access to the app entirely, if the access token is for your account, here: https://www.dropbox.com/account/security Or, you can disable just this access token using the API: v1:…

Thanks! I just tried this and I was able to reproduce the problem. (For me, it specifically gave the error ERR_UNKNOWN_URL_SCHEME.) It works properly for me in the system browser. Note that the Java SDK doesn't officially support this WebView technique though (it normally either uses the official Dropbox app or the system…

The team has been working to resolve these issues, but the error rate is still non-zero. These multiple issues appear identically to the API client though, so if you need us to check on a specific issue, please open a ticket with a new X-Dropbox-Request-Id value: https://www.dropbox.com/developers/contact

Unfortunately I don't have any specific technical information to share about the Dropbox desktop client. In short, it both listens for changes from the Dropbox servers and performs the same operations locally, and listens for changes on the local filesystem and performs the same operations on the server to match. The…

I'm glad to hear you got this working. I believe the actual cause was slightly different though. Access tokens don't expire by themselves, and will fail with a 401 if they have been revoked. It looks like the issue was instead that the cursor you were using was for a different app (the API Explorer) than the access token…

When constructing a URL, the location should be separated from the parameters by one '?', and subsequent parameters should be separated by '&'. The 'response_type' should be either 'code' or 'token', depending on which flow you want to use. You can find more information on these in the documentation here:…

The team just added a new sample to the README that shows how to use listFolder and listFolderContinue together: https://github.com/dropbox/dropbox-sdk-obj-c#rpc-style-request Hope this helps!

You can find information on how the OAuth app authorization flow works here: https://www.dropbox.com/developers/reference/oauth-guide The documentation for the specific endpoints you need to use can be found here: https://www.dropbox.com/developers/documentation/http/documentation#authorization You can use either the…

Thanks for following up Eric. I'm not sure if I understand your concern exactly though. It looks like the technique I described should work in your case. Your updateFileStatusPercent method takes the place of progressCallback in my sample above. You can add an extra parameter to updateFileStatusPercent to identify the…

Thanks for following up. Yes, please share the relevant portions of your AndroidManifest.xml as well as the code snippet(s) that reproduce this so we can look into it. (Your app key isn't considered secret, so it's safe to share, but you can open a ticket privately if you'd prefer:…

No, I don't have any news on this.

Thanks for the report! Can you let me know where you got this cursor string? Is it possible you accidentally changed it when you copy/pasted it? Also, if you can share the code from the API Explorer that works for the same cursor? Just make sure to redact your access token. Thanks!

Excellent, I'm glad to hear this is sorted out. Let us know if you run in to any other issues.

The error is reporting that the db-<app_key> URL was not available. This is the redirect URI that the SDK uses to receive the user after they go through the app authorization flow. Did you set up your db-<app_key> URL in your AndroidManifest.xml as instructed for the Android Core SDK? In any case, I should note that the…

[Cross-linking for reference: https://stackoverflow.com/questions/42635276/access-metadata-of-objects-in-dropbox-collection-shared-link ] Thanks for the post. Unfortunately, the Dropbox API doesn't currently support this link type, but I'll be sure to pass this along as a feature request. 

Hi Eric, yes, you can disambiguate the different progress blocks by setting a variable inside each. You can then factor out the rest of the handling if you want. For example: - (void)progressCallback:(NSString*)identifier bytesWritten:(int64_t)bytesWritten totalBytesWritten:(int64_t)totalBytesWritten…

There isn't a file size limit on downloads, but the HTTP requests themselves can time out if they take a long time. The "content-download endpoints", such as /2/files/download, do support Range Retrieval Requests though. That is a way of downloading portions of a file at a time, so it can be used to help avoid problems…

The equivalent of API v1's "delta" functionality in API v2 is ListFolder and ListFolderContinue. You can start by calling ListFolder, and then call back to ListFolderContinue to get any more listings as indicated by ListFolderResult.HasMore, or at a later point in the future to get any new entries. (And so on, using the…

API v2 does not return these icon values. I'll send this along as a feature request though. That being the case, the alternative is to keep your own file extension to icon mapping, and use that with the returned file extension.

Thanks for the report! I'm not seeing the same behavior though. When I access the returned profile_photo_url, I'm just getting a image/jpeg response back. Can you share a sample of what you're getting? Thanks in advance!

In the API v2 Java SDK, the equivalent would be the calling tokenRevoke to revoke the token, and then throwing the local copy of the access token.

Yes, that endpoint is considered part of API v1, so it will be retired with API v1. We have an API v2 equivalent that you can switch to instead though, at /2/auth/token/from_oauth1: https://www.dropbox.com/developers/documentation/http/documentation#auth-token-from_oauth1 Hope this helps!