Greg-DB Dropbox Community Moderator

@"sundares80" To clarify, we have not made any changes on the Dropbox servers to address this. Здравко helpfully identified a potential cause of the problem, which is that your devices may be sending an unexpected new line at the end of the request body payload. In order to validate if that is the cause of the issue, and…

@"CD12" By default, API calls to the Dropbox API operate in the "member folder" of the connected account, not the "team space". That means that by default, folders will not be created in the team space, for example. You can configure API calls to operate in the "team space" instead though, in order to interact with…

Is that all of the actual relevant code you're running? I notice you don't seem to be using the 'root_namespace_id' value anywhere. Are you calling with_path_root? Please share any other relevant pieces of code. Also, please share several more (5-10) current error outputs like this so we can look into what you're currently…

@"dwWithCat" In order to successfully use the Saver, make sure you're configuring the attributes, etc. as documented. Please refer to my previous message for a few specifics to check to make sure you configure this correctly. Also, the Saver does support uploading image files from URLs.

Your first code snippet shows you POSTing some information to your server, not directly to the Dropbox API, so it's unclear what that does. Presumably you then have code that calls the /2/files/save_url Dropbox API endpoint. That offers essentially the same functionality as the Dropbox Saver, but using a different…

Update: we confirmed this is related to sending an incorrect root for the account; in some cases the server would return a 500 instead of the expected 422 error. We've fixed that so it should be returning the proper 422 now. Please refer to the "Path Root Header Modes" documentation for information on that.

It sounds like your team may have recently migrated to the updated team space configuration, in which case your team-owned content would now be in your team space. By default, API calls to the Dropbox API operate in the "member folder" of the connected account, not the "team space". That means that by default, the contents…

@"eni8ma" A "Basic" value used in the "Authorization" header corresponds to "App Authentication". A "Bearer" value used in the "Authorization" header corresponds to "User Authentication" (or "Team Authentication"). User (or Team) Authentication are used to access a specific user account (or team). App Authentication is…

Thanks! @"sundares80" Would you be able to modify a device you have access to in order to have it not send the additional new line as a test? If you can verify that fixes the issue, I can ask the team to look into changing the server to allow that (though please note I can't make any promises on that).

@"Здравко" I can reproduce the 400 Bad Request using your code snippet, but can you clarify how you determined that this "Bad Request" issue is the cause of the problem originally reported in this thread? I don't see "Bad Request" or "400" mentioned in this thread before. The original poster seems to have reported the…

@"crunchmasterdeluxe" 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…

@"Synk" Здравко is correct; the Dropbox API requires TLS (v1.2 in particular, currently), and is currently being served with a valid certificate (from DigiCert). You generally shouldn't need to configure anything manually to be able to connect to that; the default is usually sufficient. We recommend against disabling the…

@"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…