Greg-DB Dropbox Community Moderator

Comments

  • @"eni8ma" Здравко is correct; for long-term unattended access, you should request offline access in order to get a refresh token. This only needs to be authorized by the user once manually. Refer to the following resources for more information: * https://developers.dropbox.com/oauth-guide *…
  • Yes, please refer to the information for the "How do I test my application?" question here: https://www.dropbox.com/developers/support
  • @"sundares80" While that SSL Labs SSL Server Test tool is not made by Dropbox and I am not an authority on it, my understanding is: The cipher being marked orange instead of green only indicates that the cipher is considered "weak", and does not indicate anything about the the server's use of the cipher. The inclusion of…
  • Regarding the timing, I was referring to when the requests to the link returned by /2/files/get_temporary_link are initiated. That is, if all 100 initiate their requests to the link before the account's links are banned, I would expect all 100 to complete. I would expect any requests initiated after the account's links are…
  • @"Omri1984" The combination of the two features allows an app to distinguish between all three team configurations. Please refer to this post for information on that. The recommendation is use these feature values to programmatically determine how to handle any particular team, as described throughout that post.
  • @"Omri1984" Here's a basic example of how you can use the existing root information to determine the same information as the feature values using the .NET SDK: var accountInfo = await this.client.Users.GetCurrentAccountAsync();bool team_shared_dropbox = accountInfo.RootInfo.IsTeam;Console.WriteLine("team_shared_dropbox: "…
  • It sounds like you're referring to the limits covered in this help center article. 1. It looks like this would depend on the timing and how this works in practice, see below. 1a. Yes, if the account's links are currently disabled, the /2/files/get_temporary_link call would fail with a 'not_allowed' error. 1b. I don't see…
  • @"Omri1984" The team features tell you information about the entire team itself, and the user features tell you information about the specific user account (which may be a member of a team, and so there would be some overlap with the team features). Exactly which you use is up to you, depending on what you need to know in…
  • @"burcubolek" A "path/not_found" Dropbox API error indicates that the API call failed because there was nothing currently found at the specified path in the connected account under the relevant root. For example, this can happen if there's a mistake or typo in the path value the app supplies, if the file/folder has been…
  • Regardless of what folder you're uploading to, you would use the same upload methods, such as UploadAsync in FilesUserRoutes on a DropboxClient. There aren't separate team client methods for uploading to team folders. You can upload to whatever folders (team folder or not) that the connected user account has access to.…
  • [Cross-linking for reference: https://stackoverflow.com/questions/78479669/trouble-obtaining-refresh-token-alongside-access-token-from-dropbox-oauth2-in-lo ] Whether or not you use a redirect URI, as well as where/how the redirect URI is hosted, doesn't affect whether or not a refresh token is returned. In order to get a…
  • Teams are being updated to the updated team space, though not all teams have been yet.
  • @"Omri1984" Yes, there are currently three possible team configurations. The linked resources cover how to detect all of the different feature states so apps can use the features accordingly. Note though that the 'Dropbox-API-Path-Root' header is supported by all three configurations, so you can use that to set the root…
  • @"Здравко" Thanks for writing that up! I'll pass it along to the team.
  • @"Omri1984" Здравко is correct; you can use those feature methods in the .NET SDK to make the feature calls for the team or user, but the team_shared_dropbox and distinct_member_home feature values for users and the has_distinct_member_homes feature values for teams haven't been implemented in .NET SDK yet. You can…
  • A "path/not_found" Dropbox API error, such as for the /2/files/list_folder call you showed here, indicates that the API call failed because there was nothing currently found at the specified path in the connected account under the relevant root. For example, this can happen if there's a mistake or typo in the path value…
  • While Dropbox is working to migrate teams to the updated team space, there are still teams on each of the different configurations. And yes, the best resources for information on this are: * https://dropbox.tech/developers/api-updates-to-better-support-team-spaces * https://developers.dropbox.com/dbx-team-files-guide
  • I suggest stepping through your code in a debugger, or otherwise adding logging, to inspect the content of the file data that you're uploading at each step in the process, to see where/why the value is differing from what you expect. For example, check if you are accidentally applying an incorrect layer of encoding before…
  • Do you have a file named "dropbox.py"? If so, Python would try to import that instead of the actual Dropbox package. In that case, rename or remove that file and try again.
  • Based on your other comment, it looks like you already sorted this out. Thanks for sharing!
  • This error is indicating that the app is registered for the "app folder" access type but it is setting the 'Dropbox-API-Path-Root' header when calling the Dropbox API. Apps with the app folder access type can't use the the 'Dropbox-API-Path-Root' header, because they are always automatically rooted to their app folder. To…
  • @"Dzivo" The fileBinary returned by the Dropbox JavaScript SDK in Node is a Buffer. (The fileBlob returned by the Dropbox JavaScript SDK in browser JavaScript is a Blob.)
  • @"Здравко" Can you clarify where/how you're seeing code 21 exactly and what type that is? I initially thought I had reproduced an AlertDescription 21, but I believe what I saw was actually just a record ContentType 21, which just means "alert", not a specific alert. In that case, it wouldn't necessarily indicate incorrect…
  • Update: the /2/sharing/get_shared_link_metadata and /2/sharing/get_shared_link_file endpoints (and corresponding methods in the SDKs) should now work when using an access token for an app with the app folder access type.
  • Update: the /2/sharing/get_shared_link_metadata and /2/sharing/get_shared_link_file endpoints (and corresponding methods in the SDKs) should now work when using an access token for an app with the app folder access type.
  • Update: the /2/sharing/get_shared_link_metadata and /2/sharing/get_shared_link_file endpoints (and corresponding methods in the SDKs) should now work when using an access token for an app with the app folder access type.
  • Update: the /2/sharing/get_shared_link_metadata and /2/sharing/get_shared_link_file endpoints (and corresponding methods in the SDKs) should now work when using an access token for an app with the app folder access type.
  • Update: the /2/sharing/get_shared_link_metadata and /2/sharing/get_shared_link_file endpoints (and corresponding methods in the SDKs) should now work when using an access token for an app with the app folder access type.
  • Update: the /2/sharing/get_shared_link_metadata and /2/sharing/get_shared_link_file endpoints (and corresponding methods in the SDKs) should now work when using an access token for an app with the app folder access type.
  • Update: the /2/sharing/get_shared_link_metadata and /2/sharing/get_shared_link_file endpoints (and corresponding methods in the SDKs) should now work when using an access token for an app with the app folder access type.