Recent Error - Downloading files

A path/not_found error like this indicates that there was nothing found at the supplied path for the call. In this case, you tried to download a file from a path that doesn't currently have a file, e.g., the user deleted the file. 

Thanks, is this something related as well?

com.dropbox.core.ServerException: {"error": "The server has either erred or is incapable of performing the requested operation."}

No, that error indicates a general server issue on our side. That should be relatively transient though, so you can have your app automatically retry a few times when encountering that. 

Is this still valid?
DbxEntry.File f = DbxClientV1.getFile(path, version, output)

My understanding is that DbxClientV1 should still work until mid-2017.

That's giving the message above:  "...incapable of performing the requested operation"

That's correct, DbxClientV1 uses API v1, which should continue working until June 2017.

Are you getting that error consistently? If so, please open an API ticket with the app and user ID so we can look into it for you. Thanks in advance! 

Our code for that area hasn't changed in a while (months), and we just started logging this error 2 days ago. So I don't believe it's faulty paths. Ill open a ticket.

Ok, just to be clear though, you've mentioned two different and unrelated issues:

1. com.foreflight.ForeFlightException: com.dropbox.core.v2.files.DownloadErrorException: Exception in download: {".tag":"path","path":"not_found"}:

This indicates that there was nothing found at the path specified for the download API call. This can be expected to start occurring without a code change, e.g., if the user deletes a file via the web site, desktop client, etc. Your app should be prepared to handle this exception.

2. com.dropbox.core.ServerException: {"error": "The server has either erred or is incapable of performing the requested operation."}:

This would indicate an error on our side. It can be expected to happen sometimes temporarily, If this is happening consistently though, we'd need a ticket with more information to investigate.

I just added to the ticket but the root cause appears to be a problem with .lcPath (DbxEntry), we are seeing upper-case entries.

Let me know if the fix is Java client API or if its Dropbox Server side.