Learn how to make the most out of the Dropbox Community here 💙!
Receiving Too Many Mounts error even though I do not have more than 1500 folders.
My app uses the Dropbox API to create folders, upload files and share the folders and recently I started getting an error message about exceeding the tree size. After getting this I re-organized a bunch of folders so I no longer have more than 1500 folders within 1 parent folder. I am able to create and share more folders if done through the web interface, but it doesn't seem to work through the API even after moving folders around. I get the following response when calling the /sharing/share_folder endpoint. Is there something weird going on where Dropbox 'remembers' where a folder was when it was originally shared, and even though I've moved it, it still counts as a shared folder within it's prior parent folder? {"error_summary": "too_many_mounts/tree_size_exceeded/.", "error": {".tag": "too_many_mounts", "too_many_mounts": {".tag": "tree_size_exceeded", "limit": 1500, "current_count": 1500, "new_count": 1501}}, "user_message": {"locale": "en", "text": "Your Dropbox account has reached the limit for shared folders."}} <br />
Dropbox OAuth2 Issue: Scope Parameter Handling
According to OAuth2 Authorization documentation, the scope parameter is nullable, and as per RFC 6749, parameters without a value must be treated as omitted, with unrecognized parameters ignored. However, Dropbox's OAuth2 implementation returns the following error when the scope parameter is included: Error: "error": "invalid_request", "error_description": "unknown field \"scope\"" This behavior violates OAuth2 standards, as unrecognized parameters should not cause a failure.
Slow playback when streaming with AVPlayer
We’re building an iOS App that streams mp4 video files from DropBox. We use SDK’s getTemporaryLink method and feed the returned URL to AVPlayer(url: …). The streaming doesn’t start until after a few seconds/minutes depending on the size of the file. Same issue when opening this link in a regular Safari tab. When opening the file directly in Dropbox website the video plays fine.OTA update fails in CC3200
Hi All, We are using the Dropbox API to do an OTA upgrade. We have a webclient application running on the TI microcontroller CC3200. We are using the Drop Box API from 2017 onwards, and it is working fine. When we tested the OTA functionality yesterday, it was unable to receive the CDN file URL. It is able to receive the file information from Dropbox but is unable to get the temporary link from Dropbox. Do you know what is causing this issue? Is there any recent API upgrade that has failed to respond? Please help us to fix this issue ASAP. TI CC3200 logs: sl_extLib_OtaRun: call OtaClient_ConnectServer OTA server=api.dropbox.com OtaClient_ConnectServer: http_connect_server api.dropbox.com 0 OTA run = 0 sl_extLib_OtaRun: OtaClient_UpdateCheck, vendorStr=Vid01_Pid00_Ver0302100000 OtaClient_UpdateCheck: call http_build_request /1/metadata/auto/ CdnDropbox_SendReqDir: uri=/2/files/list_folder metadata file=/Vid01_Pid00_Ver0302100000/f80_sys_mcuimgA.bin, size=142888 sl_extLib_OtaRun: OtaClient_UpdateCheck, numUpdates=1 0 OTA run = 0 sl_extLib_OtaRun: OtaClient_GetNextUpdate: file=/Vid01_Pid00_Ver0302100000/f80_sys_mcuimgA.bin, size=142888 OtaClient_ResourceMetadata: call http_build_request /1/media/auto OtaClient_ResourceMetadata: file flags=80,metadata flags=80 CdnDropbox_SendReqFileUrl: uri=/2/files/get_temporary_link 0 OTA run = 0 sl_extLib_OtaRun: ResourceMetadata CDN file URL = f= CdnClient_ConnectByUrl: ERROR, http_extract_domain_by_url, status=-1 sl_extLib_OtaRun ERROR: Failed on CdnClient_ConnectByUrl 0 OTA run = -6 OTA run = -6 OTA: Error with OTA server Regards, Sundar
I need to get all folders and nested folders within a team
Hi team! For an app we are making we need to access all folders and subfolders in a dropbox team. Just the folder names, however when calling. /2/team/team_folder/list Im only getting the top level folders, not getting the subfolders. And when calling 2/sharing/list_folders Im not getting any cursor as a response, just a list that includes around 5% of all my folders, even setting the limit to 1000 I dont get more than that. Do you know how to solve this? Thanks, Andres
Regarding the folder identifiers that are the same across users who share the folder
I need an identifier that will be the same across users who share the folder. After investigating "/2/files/list_folder" API, we were able to confirm the following: For folders for which a "shared_folder_id" can be obtained, the "id" values seen by each user are different but the "shared_folder_id" values are the same. For folders for which a "shared_folder_id" cannot be obtained (folders for which a "parent_shared_folder_id" can be obtained), the "id" values seen by each user are the same. Are the above findings guaranteed by the Dropbox API specification ? Thank you for your support.What's the actual issue with Apple FileProviders API
I'm trying to reply to this post https://www.dropboxforum.com/discussions/101001016/dropbox-on-file-provider-support-for-macos-questions/781551/replies/783389 but in a dropbox fashion "Replies have been turned off for this discussion": billgdbx can you explain exactly what is the exact issue with the Apple FileProvider API for a software engineer? What exactly does "download-on-demand" mean compared to the download now button I see in macOS finder? When I briefly read the API docs, it seems like the API should be enough; however, I've read many blog posts mentioning that the problem lies with Apple and not with Dropbox/Google/Microsoft. All these posts are blanket statements without any technical details. I'm looking for the hardcore facts, not opinions. I want to know whether I should consider ditching apple? Or dropbox? If there is an issue at apple's side - I want to know what it actually is so I can make my own decisions rather than being treated like an idiot and a fool. In my experience, dropbox announces all breaking changes to customer as ultimatums without any true explanation. Now that I think about it... it is actually coming from disrespect and even contempt to your customers.
list_shared_links API inconsistency with team folders: Only showing edit OR view link, not both
I'm encountering an unexpected behavior with the list_shared_links API (https://api.dropboxapi.com/2/sharing/list_shared_links) when working with team folders. I hope someone can provide clarification. Issue: When listing shared links for a team folder that has both edit and view links: 1. If both edit and view links exist, only the edit link is returned in the API response. 2. If I remove the edit link manually, then only the view link is returned. But, if I pass the specific path it return both links Details: - I'm using a team access token. - I'm passing the 'Dropbox-API-Path-Root' header to list all team space shared links. Expected behavior: Based on the API documentation, I expected to see all shared links returned. The docs state: "If no path is given, returns a list of all shared links for the current user. For members of business teams using team space and member folders, returns all shared links in the team member's home folder unless the team space ID is specified in the request header." Steps to reproduce: 1. Create both an edit and a view link for a team folder in Dropbox. 2. Use the list_shared_links API with a team access token and the 'Dropbox-API-Path-Root' header, without specifying a path in the body. 3. Observe that only the edit link is returned. 4. Manually remove the edit link for the folder via the Dropbox dashboard. 5. Use the list_shared_links API again with the same parameters. 6. Observe that now only the view link is returned. Questions: 1. Is this the intended behavior of the API for team folders? 2. If so, is there a way to retrieve both edit and view links for team folders in a single API call without specifying the path? 3. If not, is this a known issue specific to team folders, and is there a workaround or fix planned? 4. Does this behavior differ between team folders and personal folders? Any clarification on this would be greatly appreciated, especially regarding how the API is supposed to handle multiple link types for team folders. Thank you!