We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
anonymous
5 years agoSystem.AggregateException path/not_found
I am trying to builg a simple app to extract a file from dropbox and save it on my computer. I have verified the token, the files exist on dropbox, it's location and the directory on my computer. T...
- 5 years ago
A 'path/not_found' error like this indicates that there was nothing found in the connected account at the path specified by the app. In this case, that's specified by the parameter value you're giving to the DownloadAsync method, which you're building from `folder + "/" + file`.
Those actual values are mostly redacted from your screenshot, but I do see that you have "?dl=1" at the end of your `file` value. Unless you actually have at the end of the filename of the file in your account, you shouldn't be appending that. That's just an option for use with shared links, not for file paths themselves.
Also, note that if your app is registered for the "app folder" permission, all file paths will automatically be interpreted relative to the special app folder automatically made for your app, inside "/Apps" by default. In that case, make sure the file(s) you're trying to work with are actually inside that app folder.
You can use the ListFolderAsync/ListFolderContinueAsync methods to list the contents, if any, of the root folder, by starting with a 'path' value of the empty string "". That way you can get the actual Metadata.PathLower value for downloading a file with DownloadAsync.
Greg-DB
5 years agoDropbox Staff
A 'path/not_found' error like this indicates that there was nothing found in the connected account at the path specified by the app. In this case, that's specified by the parameter value you're giving to the DownloadAsync method, which you're building from `folder + "/" + file`.
Those actual values are mostly redacted from your screenshot, but I do see that you have "?dl=1" at the end of your `file` value. Unless you actually have at the end of the filename of the file in your account, you shouldn't be appending that. That's just an option for use with shared links, not for file paths themselves.
Also, note that if your app is registered for the "app folder" permission, all file paths will automatically be interpreted relative to the special app folder automatically made for your app, inside "/Apps" by default. In that case, make sure the file(s) you're trying to work with are actually inside that app folder.
You can use the ListFolderAsync/ListFolderContinueAsync methods to list the contents, if any, of the root folder, by starting with a 'path' value of the empty string "". That way you can get the actual Metadata.PathLower value for downloading a file with DownloadAsync.
- anonymous5 years ago
Greg,
Thank you so very much for the explanation!
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
5,877 PostsLatest Activity: 12 months 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!