Greg-DB Dropbox Community Moderator

@"Bk13" If Dropbox is repeatedly unable to successfully deliver webhook notifications to your webhook URI server, it will stop attempting to do so. At that point, your webhook URI will be disabled, you will be notified of this by email, and no further webhook notifications will be sent until the webhook URI is re-enabled.…

@"qaaperture" Здравко is correct; the Dropbox API does not currently support modified times for folders, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though.

@"synology_support" I just wanted to follow up here to let you know we've recently received several samples from users regarding this thread. I believe we've established enough of a pattern here that we do not require any further samples, so there's no need to send in more samples. I'll let you know if the team requests…

Please note that the files_list_folder/files_list_folder_continue interface is paginated, so you're not guaranteed to get all results back in a single page. The number of pages that are used can change over time and across accounts, folders, etc. Be sure to check the ListFolderResult.has_more returned by files_list_folder.…

@"Vlopez1" Given the description of the issue, such as how it works for you locally and only fails sometimes when using the remote device, it does sound like a transient network issue. While it wouldn't fix any network issues, you can configure the timeout for the Dropbox client using the "timeout" parameter on the Dropbox…

@"SJ_Code" It looks like your messages got caught in the spam filter for some reason. I just released them. Unfortunately I don't have a timeline to share for updates to the .NET SDK.

A server update caused unencoded header values to be rejected. We’ve updated the server to accept these requests again so this should be working now. However, the .NET SDK should have automatically handled this for you anyway, so we would still want to check on that. If possible, please share the answers to the questions…

@"awb" This was due to an incompatibility between the format of certain responses returned by the API and how the SDK was parsing them. The team updated the server to return responses that the SDK would parse successfully. There may be other cases of this though, so if you're seeing this currently, please share several…

Dropbox is no longer offering the option for creating new long-lived access tokens. Dropbox is now issuing short-lived access tokens (and optional refresh tokens) instead of long-lived access tokens. You can find more information on this migration here. Apps can still get long-term access by requesting "offline" access…

Thanks for sharing this. I tried out this code though, and it worked successfully for me. Can you confirm if this was the exact code that produced the error you saw? For instance, did you change any of the parameter values after you reproduced the issue before you posted this? If so, please share the actual parameter…

@"Nico-Uretek" I don't actually see any encoding being done on your header values in your code. Please make sure you have the encoding implemented as covered here.

@"Nico-Uretek" If you're still seeing an issue when applying the encoding as documented, please share the specific steps, code, and parameter value(s) needed to reproduce the issue you're seeing so we can look into it. Be sure to redact any access/refresh tokens though. Thanks!

Thanks for confirming simotin13!

As Здравко mentioned, please make sure you're encoding header values as documented here: https://www.dropbox.com/developers/reference/json-encoding

@"SJ_Code" I can only help with API matters, so if you have any questions regarding the UI or the state of your team itself, I recommend reaching out to support. But yes, has_team_shared_dropbox is only true for the non-updated team space configuration. As for your questions: 1. Yes, a team gets upgraded as a whole, so…

@"dsmurfin" The examples I included in my previous message happened to be for the (non-upload session) "upload" method, but the upload session methods also support the same three ways of supplying file contents. For instance, here are the three versions of the uploadSessionStart method: * uploadSessionStart taking Data *…

@"SJ_Code" 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 determine the same information from the RootInfo object in the FullAccount returned by GetCurrentAccountAsync though: *…

Thanks for the report. We'll look into it. It looks like sending "{}" (instead of "null") still works. Can you try sending "{}" instead of "null"?

@"dsmurfin" The SwiftyDropbox methods for uploading files accept file data as Data, URL, or InputStream. For example, here's the three versions of the "upload" method: * upload taking Data * upload taking URL * upload taking InputStream Can you try URL or InputStream instead and see if that works for you?

It looks like you’re experiencing an issue with a third party application that integrates with Dropbox. Please reach out to the support organization for that third party app for help. If the developers of this app are having any trouble with the Dropbox API itself, they can reach out to Dropbox developer support directly…

That's correct, while this is not officially documented, you can put a tag as the search query for /2/files/search_v2 to search for the tag. For example, in the Python SDK, along with setting the "folder" category, that would look like this: result = dbx.files_search_v2(query="#testingtag",…

@"rororo12" Like Здравко recommended, I suggest troubleshooting your environment to see if there's anything wrong with your network connection that would be interfering with the network requests to the Dropbox API servers. (For example, is there any proxy, firewall, etc. that may be causing an issue?) I'm not aware of an…

@"Korefer87" Rich is correct. Dropbox issues short-lived access tokens, which expire after a few hours, and optional refresh tokens, which don't expire. Apps can get long-term access by requesting "offline" access, in which case the app receives a "refresh token" that can be used to retrieve new short-lived access tokens…

You can use /2/files/search_v2 to search for items, and set options.file_categories to "folder" to restrict the results to folders only. Refer to the documentation for more information. You can also try out calls using the API v2 Explorer.

@" blueli" As Здравко said, you can save the latest received cursor (whether from /2/files/list_folder or /2/files/list_folder/continue) and call /2/files/list_folder/continue again later to get the new changes since then; at that point you can then save the new cursor returned by /2/files/list_folder/continue. You don't…

For more information on using refresh tokens with Dropbox, refer to the following resources: * https://www.dropbox.com/developers/documentation/http/documentation#authorization * https://developers.dropbox.com/oauth-guide * https://dropbox.tech/developers/using-oauth-2-0-with-offline-access

@"bipulkumar3103" Also, note that apps with the "app folder" access type can't use team scopes, and so the team scopes section isn't shown for such apps. You'll need an app with the "full Dropbox" access type to use team scopes. It's not possible to change the access type on an existing app, but you can register a new one…

@"lfranchi_pilot" I see you only mentioned using /2/files/list_folder, so make sure you've also implemented /2/files/list_folder/continue as documented. You're not guaranteed to get everything back in one call. Using the Dropbox-API-Path-Root allows you to set a different root for an API call. For example, you can use that…

@"prabhat1999" Make sure you're supplying a valid path. For example, make sure your path doesn't end with a "/". It looks like there's a bug where the server incorrectly returns a ''malformed_path' error as 'not_file'. I'll ask the team to fix that up, but you can avoid that by supplying a properly formatted path. Update:…

@"sundares80" I don't have any news on this right now. I'll check in with the team.