You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
snaidamast
5 years agoExplorer | Level 3
DropBox API Async Call, "DropBoxClient.Files.DownloadAsync" will not throw an exception (solution)
Issue:
I have been using DropBox for the storage of my new document management application's installation file as well as for updated, individual files that can be downloaded at a later date (after the initial installation).
Upon testing the following async call, DropBoxClient.Files.DownloadAsync, I saw that if a file has not been uploaded to my DropBox folder, where all of these application files are to be stored, this call will throw a "path not found" exception (which makes sense).
However, instead of having this error caught by my code's try-catch construct, the application being tested simply ends.
According to replies from DropBox developers in and around 2017, this was a known issue with their API SDK, and consequently would be fixed. However, my own testing for the past day or so appears to have shown that this issue still exists, even with latest version of the DropBox SDK\API, which I implemented using the NuGet Package Manager.
Solution:
I decided to test another async call to see if this situation is common to all of the DropBox API async calls or was merely an issue with the aforementioned async call.
As a result, I tested the following call prior to DownloadAsync call to see if a "path not found" exception would be caught as hoped.
Using the following call, DropBoxClient.Files.GetMetadataAsync, which merely retrieves the meta-data for the specified file, if the file does not exist in my DropBox folder, it will in fact throw the "path not found" exception and the exception will be caught properly with a try-catch construct...
As a result, if you are experiencing a similar issue with your code, simply use the DropBoxClient.Files.GetMetadataAsync call prior to the actual download call to test for your file's existence, while having the ability to trap for an error exception if one arises.
- Greg-DBDropbox Staff
While you can certainly call GetMetadataAsync first, you should be able to directly catch an exception from DownloadAsync in the Dropbox .NET SDK using a catch block.
I just gave this a try myself using the latest version of the Dropbox .NET SDK, currently v5.0.0, and it is working for me. I am able to catch the exception from DownloadAsync and see the 'path/not_found' error, without my app's execution ending.
Can you let us know more about the issue you're seeing so we can look into it? For instance, please share:
- the name and version number of your environment, e.g., what Visual Studio you're using
- the steps to reproduce the issue, such as the relevant code snippet(s)
- the full error/output you get
Thanks!
- snaidamastExplorer | Level 3
Hi Greg:
I am also using the 5.0.0 version of the DropBox API.
And yet with the DownloadAsync call, if a "path not found" error is thrown, the entire application abrubtly ends. This is not occurring with the GetMetadataAsync call.
I am developing in VB.NET with Visual Studio 2019 under .NET Framework 4.6.
There is nothing I can show you since there are no error messages that are being displayed in any way. I just try to manual trap such a situation when I am testing the applictaion...
- Greg-DBDropbox Staff
Can you also share the relevant code showing how you're making the call and attempting to catch the exception so we can try to reproduce that the same way here? Thanks in advance!
About Discuss Dropbox Developer & API
Make connections with other developers
795 PostsLatest Activity: 23 hours agoIf you need more help you can view your support options (expected response time for an email or ticket is 24 hours), or contact us on X or Facebook.
For more info on available support options for your Dropbox plan, see this article.
If you found the answer to your question in this Community thread, please 'like' the post to say thanks and to let us know it was useful!