Greg-DB Dropbox Community Moderator

Thanks! I can't seem to reproduce that issue though. This works correctly for me: $.ajax({ url: 'https://api.dropboxapi.com/2/files/get_metadata', type: 'POST', processData: false, data: JSON.stringify({"path": "/Recipes"}), contentType: 'application/json', headers: { "Authorization": "Bearer <APP FOLDER ACCESS TOKEN>" },…

I don't have an ETA for a fix right now. I'll post here once I have an update.

You mentioned your app has an app folder, so can you double check that the app folder itself contains a "Recipes" folder in it? I.e., when you look at dropbox.com, that would be at /Apps/<app folder name/Recipes. Also, if you've registered multiple apps or used multiple accounts, make sure you're using an access token for…

Is the get_file_and_metadata call running successfully? It sounds like that error message is coming from your Firebase database method, so I'm afraid I can't be of much help here. You may want to refer to the documentation/support channels for that instead. Also, note that you're using Dropbox API v1, which is deprecated.…

That's correct.

Thanks for the report attic! That's the same issue as the one volkeru reported. We're working on it.

Thanks for the feedback!

[Cross-linking for reference: https://stackoverflow.com/questions/41537788/how-to-use-proxies-with-dropbox-api ] You should be able to create a requests session with proxies using dropbox.create_session and pass that to dropbox.Dropbox as the session parameter. [MODERATOR NOTE: BROKEN LINKS WERE REMOVED]

The simplest solution is to upload files serially, but alternatively, we do have a data ingress guide here that covers this issue and details how you can avoid this issue by committing files in batches: https://www.dropbox.com/developers/reference/data-ingress-guide Hope this helps!

Unfortunately, there isn't currently a good solution here. After you move/rename a file, listing the revisions at the new path won't show the old revisions. As a workaround though, you can call to list the revisions at the previous path, and they will still be there.

No, Dropbox doesn't offer anything quite like that, but I'll be sure to pass this along as a feature request.

Thanks for the request ID volkeru! That one happens to be a different issue than the one originally reported on this this thread, but it is also a known issue we're working on.

No update on this unfortunately.

I don't believe we have any examples quite like that for the API v2 Java SDK, but I'll be happy to help with any issues you're running in to. The basic idea is that you can call listFolder and listFolderContinue initially until hasMore is false to get the initial state. Then, you can listFolderContinue for the relevant…

No, no update on this right now. I can't promise if that would work as a workaround, as each case may be different, but it may help.

To follow up here, if you do need to migrate OAuth 1 access tokens and want to do so via API v2, we now have an API v2 endpoint for doing so: https://www.dropbox.com/developers/documentation/http/documentation#auth-token-from_oauth1

To follow up here, we do now have an API v2 version of this: https://www.dropbox.com/developers/documentation/http/documentation#auth-token-from_oauth1

No problem, that would look like this: [DropboxClientsManager setupWithAppKey:@"APP_KEY"]; DBTransportClient *transportClient = [[DBTransportClient alloc] initWithAccessToken:nil selectUser:nil baseHosts:nil userAgent:nil backgroundSessionId:nil delegateQueue:nil appKey:@"APP_KEY" appSecret:@"APP_SECRET"];…

Thanks for the additional information! I can't reproduce this issue using your code though, so it does seem there's something else going on. I took a closer look at the output you shared, and the PAC/proxy messages cite error 1022, which is NSURLErrorAppTransportSecurityRequiresSecureConnection. That indicates it is the…

The other output seems to indicate that you may be trying to use a proxy, configured via a pac file. Is the pac file hosted on HTTP? Otherwise, can you share the rest of the code? What you shared was incomplete. I'll be happy to try to reproduce it.

The Dropbox API operates entirely over HTTPS, so it shouldn't trigger a message like that. Are you sure that's the only thing running when you get this?

Thanks! We'll look into it.

That is the right way to do this, but it looks like the curl example in the documentation for /2/auth/token/from_oauth1 is unfortunately incorrect. I'll let the team know to fix that. That endpoint actually uses app authentication, so an OAuth 2 access token isn't necessary. This is what the curl example should look like:…

If the file isn't found, your catch block should get run, with the data variable containing the error information. Is that not running for you?

Thanks for the report! This is a known issue, but I don't have a timeline for a fix right now.

Yes, it sounds like you want the /2/team/members/get_info endpoint: https://www.dropbox.com/developers/documentation/http/teams#team-members-get_info That lets you look up one or more team members by suppling any of team_member_id, external_id, or email.

Hi Joel, a server exception like this indicates an issue on our side. These are usually transient, so you can just have your app retry these calls. It looks like we did have a spike of errors earlier today, but that should be resolved now. If you are able to reliably reproduce any of these though, please share the steps to…

When using the Business API, the rate limiting for the team endpoints are similarly per-team, not per app. For the user endpoints, it is per-team member. We don't have any specific numbers available though.

Thanks! We'll take a look and respond to your ticket soon.

Thanks for the feedback! As it is designed the format of the response is not dictated by the format of the request, but rather can be determined programmatically by checking the response Content-Type. I'll send this feedback along to the team though.