Greg-DB Dropbox Community Moderator

Thanks for the additional information. To be more specific, from your description here, you would need to change this line: team_client = dropbox.team.DropboxTeam(credential.access_token) by replacing "dropbox.team.DropboxTeam" with "dropbox.DropboxTeam". That would make the fixed line look like this: team_client =…

The DropboxTeam class is defined as dropbox.dropbox_client.DropboxTeam, so you can access it from dropbox.dropbox_client; it's also available on just dropbox. (I see your dropbox-test.py and dropbox_utils.py examples actually do this differently from each other, which seems to explain the discrepancy; the former imports…

I see you're getting an "Invalid select user id format" error, which indicates that the value you're sending in the "Dropbox-API-Select-Admin" header is not of the expected format. That seems to be coming from your credential.team_member_id variable. Note that "Dropbox-API-Select-Admin" (and "Dropbox-API-Select-User")…

I don't have an update on this currently. I'll follow up here once I have any news.

The dl=1 parameter is meant for downloading a file in a browser, so if you want to programmatically retrieve the file data, you may want to use raw=1 instead of dl=1. I just tried it and raw=1 returned a 'content-type: image/png' (after the redirect), for example.

You can find the official documentation for this here: https://help.dropbox.com/share/force-download In short, the recommendation is not to change the hostname, but to parse the URL (as opposed to doing string replacements) to change the URL parameters as needed, and make sure your client can follow redirects automatically.

No, unfortunately I don't have information on the timeline for this.

Thanks for the report! We looked into this and found an issue affecting this link. It should be working again now. Please try again and let us know if it's still not working for you though.

Thanks for the feedback! As you found, the Embedder is the closest thing we have to this currently, but it unfortunately does not support videos; I'll pass along this feature request, but I can't promise if or when that might be implemented though.

For reference, please refer to the documentation for specific information on what each field means. We cannot make guarantees beyond what is in the documentation. To confirm, both shared folders and team folders are considered a type of "shared folder. For the metadata returned by /2/files/get_metadata (as well as…

Thanks for trying that and confirming it works in the system browser and following up with the additional information. That being the case, can you update the app to process the authorization flow using the system browser instead of a web view? Per the Dropbox /oauth2/authorize documentation, this flow is not meant to be…

@"cesdewar" It sounds like my reply from 5/7 didn't make it to you. I've copied it below for reference: Thanks for following up. Your reply was caught by a spam filter; I've now recovered it. It looks like you're processing the OAuth app authorization flow in a web view in your app. Can you also try it out in the system…

Thanks for following up. Your reply was caught by a spam filter; I've now recovered it. It looks like you're processing the OAuth app authorization flow in a web view in your app. Can you also try it out in the system web browser itself on the device and let me know if the issue does or doesn't reproduce there as well, and…

Based on this information, it looks like this is referring to the links returned by the Dropbox API /2/files/get_temporary_link and /2/files/get_temporary_upload_link endpoints, for getting links to download and upload files from/to Dropbox, respectively. Those endpoints return links using the mentioned hosts/formats.…

Thanks for the feedback! I'll send this along to the team, but I can't promise if/when that change would be implemented.

That's correct, the 'limit' parameter on the /2/files/list_folder endpoint is a way to request an approximate upper bound on how many entries to return. The /2/files/list_folder endpoint, whether or not used with the 'limit' parameter, does not offer a minimum number of entries per page, however. Due to some specifics of…

Unfortunately it's not possible to add additional owners/developers to an app, such as to allow other accounts to view/configure an app's settings on the App Console, but I'll be sure to pass this along as a feature request. I can't promise if or when that might be implemented though. 

Thanks for the report. This sounds like a different kind of issue than the one in your original thread, so I've moved this to its own thread. Are you still seeing this issue now? If so, can you let me know the specific steps to reproduce it? It may be helpful if you can share a short screen recording showing the issue. I'm…

SharingFileLinkMetadata and SharingFolderLinkMetadata are each subtypes of SharingSharedLinkMetadata; they aren't three distinct types. So given a SharingSharedLinkMetadata, 'file' indicates a SharingFileLinkMetadata, and 'folder' indicates a SharingFolderLinkMetadata.

@"Sc0rp0w" App folders are incompatible with shared/team folders, meaning you can't share an app folder, put a shared/team folder inside an app folder or put an app folder in a shared/team folder. (The app folder name setting only allows you to set the default name of the app folder, not the full path, so you can't use…

@"TStack" Yes, refresh tokens do not expire automatically, so they can be used reliably for long periods of time, even years. Be aware though that refresh tokens/access tokens can be revoked on demand by the app or user.

@"TStack" Can you clarify what you mean by "sustainable"? 

@"TStack" If you're referring to any long-lived access tokens retrieved before the switch to short-lived access tokens and optional refresh tokens, note that while the creation of new long-lived access tokens is no longer available, we don't currently have a plan to disable existing long-lived access tokens. (If that…

Thanks for the feedback! I'll pass this along as a feature request, but I can't promise if or when it might be implemented.

This should be working now. Please let us know if you're still seeing any issues. Thanks for the report!

New update: The team has developed a new solution that should allow these requests with the extra new line to succeed. We've deployed this solution for all requests and expect to be able to keep it deployed permanently. Please note that we do still ask that you update your client code to avoid sending the extra new lines…

@"athithan" Can you try again and let me know if you're still seeing this issue now? Thanks!

Apologies for the delay in updating this thread. This error should no longer be occurring. Please let us know if you're still seeing any issues.

@"sisrael1" Yes, multiple concurrent uploads can trigger this lock contention error. Refer to the resources in my previous post for information on how to commit multiple changes in one call to avoid triggering lock contention with your own changes.

@"sisrael1" Also, note that if there are multiple changes at the same time in the same account or shared folder, you can run in to this 'too_many_write_operations' error in particular, which is "lock contention". That's not explicit rate limiting, but rather a result of how Dropbox works on the back-end. This is a…