We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
List_folder does not return team folders
Hi guys,
Two days ago our automated tests started failing out of the blue. We were checking that "/files/list_folder" returns both shared and team folders, but since then team folders have not appeared in the response. Were there any recent changes related to that in DropBox API?
We are using https://www.nuget.org/packages/Dropbox.Api/4.9.0 library, `DropboxTeamClient` with `AsMember` set (to list folders of a specific user), `client.Files.ListFolderAsync("")`. It is a stable app, we haven't done changes in years.
Update, I have just updated to the latest https://www.nuget.org/packages/Dropbox.Api/6.30.0 , but the response is still the same (no team folders).
Sincerely,
Jakub
I'm not aware of any changes that should have caused this, but there are a number of possible things that might have occurred here.
First, you mentioned using ListFolderAsync, but have you also implemented ListFolderContinueAsync? That interface is paginated and does not guarantee all entries will be returned on a single call to ListFolderAsync. You should always check ListFolderResult.HasMore and if it's true, call back to ListFolderContinueAsync fore more entries. You can find more information in the ListFolderAsync documentation. The exact number and set of entries returned on any individual page can vary over time, due to folder structure and activity, etc.
Otherwise, there are a number of other things that might have affected this, such as:
- the shared/team folders were unshared (either entirely or just from the relevant member)
- the team switched to the team space configuration; see the Team Files Guide for more information
- the team was disbanded
If you still need help sorting this out, feel free to open an API ticket with the relevant member ID (but don't share any access/refresh token).
- Greg-DB
Dropbox Staff
I'm not aware of any changes that should have caused this, but there are a number of possible things that might have occurred here.
First, you mentioned using ListFolderAsync, but have you also implemented ListFolderContinueAsync? That interface is paginated and does not guarantee all entries will be returned on a single call to ListFolderAsync. You should always check ListFolderResult.HasMore and if it's true, call back to ListFolderContinueAsync fore more entries. You can find more information in the ListFolderAsync documentation. The exact number and set of entries returned on any individual page can vary over time, due to folder structure and activity, etc.
Otherwise, there are a number of other things that might have affected this, such as:
- the shared/team folders were unshared (either entirely or just from the relevant member)
- the team switched to the team space configuration; see the Team Files Guide for more information
- the team was disbanded
If you still need help sorting this out, feel free to open an API ticket with the relevant member ID (but don't share any access/refresh token).
Hi Greg,
thank you for your response. Yes, we are using ListFolderContinueAsync, that is not the problem. But your suggestion gave me an idea to check the activity log and this is what I found:
Please note, that "Y3S.dev Team Folder" is the folder which we were expecting in our test in the team member root folder. Do you have any idea what could that be and what could caused it? Is there a way how to change the parent back so it is in team member folder again?
- Greg-DB
I can't say for sure exactly what happened off hand, but it sounds like a team admin may have changed the folder structure and settings. You may want to contact support for help investigating and potentially reverting whatever changes were made. (Or if you're not an admin on the relevant team, it may be best to have them do so.)
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
