So...I made a call to `list_shared_links` precisely because a call to create a shared link said the link already existed...I didn't cache some of them originally...so I was writing code to detect this error and list shared links so it could cache them...but it's saying I have no files in a folder I know that I do....
But when I had it list all shared links without a path...it showed other folders...I copied the path line from the results and used it in a curl call...and it showed no shared links either...despite the fact it did in the API Explorer...but only if you put no path in...
Any help with this would be appreciated. I can't create new shared links to the files I'm calling for because it says they already exist...so my hands are tied.
The previous is one of my debug lines...the error returned has metadata/.., but sometimes it's ..., or ., sometimes no dots...I'm not sure if this is a Dropbox thing...or some byproduct of the Go library I'm using to access the Dropbox API.
"If no path is given, returns a list of all shared links for the current user."
"If a non-empty path is given, returns a list of all shared links that allow access to the given path - direct links to the given path and links to parent folders of the given path."
So, supplying as path to a folder will not make it list the shared links for files inside that folder. If you want the shared links for a file, you need to specify the full path for the file.
Also, the variable anount of trailing periods are intentionally added by Dropbox, to discourage clients from doing exact string matching on these error string, in favor of prefix matching. This way, we can add nested errors without breaking clients.