We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
.NET API : DropboxClient.Sharing.AddFolderMemberAsync() no more completing
Hello, Since yesterday, DropboxClient.Sharing.AddFolderMemberAsync() has stopped working (while all other API calls still work). Basically, I'm just creating a new team folder and then assigning 4 m...
Hi Greg,
Like I said, imho there is no activity that could explain the error here. The shared folder has just been created and there is absolutely no activity on my dropbox account on the desktop or on the web. The only activity for the folder / account consists in a single API call for adding 4 members to the newly created folder. If that only can result in that kind of exception, I wonder whether the API is really usable for automating complex tasks.
But forget about the "too_many_write_operations", I worry MUCH more about the other behavior : the "await AddFolderMemberSync" that never ends. Requested changes are made right after the API call (I can view the correct memberships in the admin console), but even after one hour the application still "await" the API call. If some calls to the API never return (no KO nor OK nor exception... just nothing), it makes all programming work uneffective and the full API useless! What can be done to monitor what happens? Should I open a support ticket? Thanks for your advice.
The API always returns (with either success or some error). What you're talking about is Dropbox .Net SDK though - make difference. 🙂 It's different thing and, by idea, it's supposed to make your life easier. As seems, in your case, something makes the SDK to think API call never finish and that's why it blocks. This SDK always returns when entire request finished, for all non download requests (as is in your case), something that makes debugging of such issues difficult unfortunately. You may want to pass your own HTTP client, with customized handler, that will let you follow what exactly happens or to re-implement on your own the particular call only. If I am in your shoes, I will do that (one of the both). In such a way you will have much more detailed view of what happens and see where exactly is the issue. Also, you will be able see the request ID that may help further debugging (.Net SDK provide it on clearly identified error only). Do it! 😉
Good luck.
Thank you Здравко for the advices. I'm not used to programming direct calls to APIs using http clients, but I'll give it a try 😉
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
