Greg-DB Dropbox Community Moderator

I'm not aware of any current disruption that should be causing that. I'll be happy to help this, but I'll need some more information. Please reply with: * the name and version number of the platform and SDK/library/HTTP client you are using, if any * the steps to reproduce the issue, including relevant code snippet(s) *…

Thanks for following up. I'm glad to hear you got this sorted out. And thanks for the feedback! I'll send this along to the team.

@"duckladydinh" No, unfortunately there currently isn't a way to download a whole sub-folder from a a shared link for a folder via the API, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. Note that you can download the top-level folder as a zip from the shared…

@"quartertone" No, unfortunately I don't have any news on this request.

We're not currently experiencing any known service disruption that would cause empty replies from the Dropbox API. Might there be something on your network connection preventing your app from connecting to the Dropbox servers? For example, might there be some firewall, proxy, or caching layer that is either blocking or…

I see that you are checking the 'IsComplete' status of the UploadSessionFinishBatchAsync job using UploadSessionFinishBatchCheckAsync, but that will only tell you if the operation is complete overall. It does not indicate whether any particular commit succeeded or not. You should additionally check…

@"duckladydinh" I'm not sure I understand your comment. If something isn't working as documented, please share the details so we can look into it for you. For example, you can use the /2/files/list_folder endpoint to list the contents of a folder from a shared link for the folder: curl -X POST…

It sounds like your team is set up to use the "team space" configuration, so you shouldn't use the /2/team/team_folder/* endpoints. To create a folder in the team space, you should use the /2/files/create_folder_v2 endpoint. Please refer to the Namespace Guide for information on how to operate in the team space. 

Yes, I'll follow up here once I have an update on this. I can't promise when that will be though.

@"steve-the-bayes" Thanks for letting me know! I've fixed the documentation links in my earlier message.

You should send them as POST parameters, encoded using "application/x-www-form-urlencoded", not headers. Here's a basic example I just put together for calling /oauth2/token using curl in PHP: $app_key = "<APP_KEY>"; $app_secret = "<APP_SECRET>"; $headers = array("Authorization: Basic " . base64_encode($app_key . ":" .…

When using "Basic" authorization, your "Authorization" header value should start with the string "Basic ". So, that line should look like: "Authorization: Basic " . base64_encode($app_key . ":" . $app_secret), Also, note that the /oauth2/token endpoint is based on the OAuth spec and doesn't work like the other Dropbox API…

I see you opened a new thread for this with more information so I'll follow up with you there.

In that case I recommend checking the documentation for how to access the URL parameters for the URL from Apache in PHP. Those aren't made by Dropbox so unfortunately I can't provide specific guidance for that. (It sounds like you're making a web app though so do make sure you are using you're using the "code" flow and not…

This appears to be a duplicate of this thread, so I'll close it and follow up with you there.

Thanks for writing this up! This does seem to be a bug in the SDK. The UploadSessionFinishArg type has a 'contents' field because it's how you supply the data if/when calling filesUploadSessionFinish (not the batch version), where it gets set as the request body, but it's not actually needed or expected…

Can you elaborate on what you mean when you say you are "unable to receive code in the redirect URI"? What are you trying, and what isn't working as expected? For using the OAuthResponseType.Code flow, I recommend checking out the SimpleBlogDemo example, which has that implemented here:…

When calling /oauth2/token, you can actually pass the app key and secret either as 'application/x-www-form-urlencoded' (not JSON) POST parameters, or in the place of the username and password, respectively, in "HTTP basic authentication", that is, in the "Authorization" header. You can find more information on that in…

You can find examples of the information included on the redirect URI after the user authorizes the app in the /oauth2/authorize documentation, under the "Returns" section: https://www.dropbox.com/developers/documentation/http/documentation#oauth2-authorize Specifically, there is a "Sample response" for both the code and…

Thanks for confirming! Unfortunately, no, I can't think of a more direct or faster way to query that information. 

I'm not sure I understand your specific scenario here, but it sounds like you may want to use the /2/sharing/get_folder_metadata endpoint. You could supply the team or shared folder ID as the shared_folder_id, which would give you the 'parent_shared_folder_id' value. You could then call again with that ID to get the…

@"dgo" Please update to the latest version of the SDK, currently v3.1.3, and let me know if that doesn't help. @"dgsqrs" Likewise, if you're not already using v3.1.3, please update to it and try again.

Thanks for the report. I'll check on this with the team again.

That's just some of the response headers, but not the response body. Can you print out the response body too?

Yes, that's correct, given that both the official Dropbox iOS app and the official Dropbox web site do not support iOS 9, the Dropbox OAuth app authorization flow is also not supported on iOS 9. (Technically, you might be able to implement a system where the user processes the authorization flow on another computer/device…

Thanks for writing this up. I'm afraid I don't have a workaround to offer here though. The Dropbox website unfortunately does not support the older browser on iOS 9, so it will be prone to incompatibilities like this.

The API and SDK should be working, and they are working for me in my testing. What version of the SDK do you have installed? If you're not using the latest version, currently v3.1.3, please upgrade to that and try again.

Thanks for following up. I'm glad to hear you already tracked this down. Yes, due to some implementation details on the backend, you shouldn't rely on the size of the "events" array. You should always check "has_more" itself.

Please print out the response body. It should contain a more useful error message indicating what the issue it.

There isn't anything additional you should be doing. Both of these fields are marked optional and may not always be available, for various reasons, e.g., due to a historical data gap. You can find more information on the different fields in the documentation here.