Child Item

new device error - DownloadErrorException: Exception in 2/files/down

I have developed an app that operates well on a Samsung Tablet ("Tablet1"). I have now loaded the app onto a different Samsung tablet (same model-"Tablet2") but find that when I try to download the file from the "Tablet2" I get the above error. The file and path remain the same in both instances.

Is there something I am not aware of that I need to do from "Tablet2" ? Or does "Tablet2" need to be identified to Dropbox to give it permission to download this file?

Thanks

Brad

Find more posts tagged with

API

Abuse

Accepted answers

Здравко

@BradHenderson wrote:
... I thought I could just load the app onto a different device provide the app with correct token and Dropbox would give access to the new device. ...

@BradHenderson, That's something normal and expected to be as you think. For some reason (i.e. some mistake) it's not. You should debug your application starting with finding that reason out. That's what I advised you to do, not something else.

Hm..🤔 Let's say it in other words. Where did you get that non existing file path/id from - is it something hard coded or...? Hard coding of such thing is not a good idea - it predisposes for errors and confusions! Can you "fix" your code not to assume particular file (or any place at all), but to look for that file (place of file) using navigation with listing account content starting from account/namespace root? This root path is ALWAYS correct and has the same form - just empty string (the same for ALL accounts - no chance for error or confusion). In such a way, whatever happens, you will be able see it while navigating in your application user interface (and understand when/what is going wrong, not just guesses). Everything else would be speculation. Even more, it wouldn't be possible to select non existing file in such a way (it wouldn't exist in the lists too where you're going to get everything from). 😉 Such non-existing file is possible only when you assume something - something that's not true or not entirely true in particular situation. There are lots of possibilities and instead of guessing what's there, just take a look.

Hope it's a bit more clear now.

All comments

BradHenderson

Sorry I realised the error message is incomplete in the heading I am getting this error:

(DownloadErrorException) com.dropbox.core.v2.files.DownloadErrorException: Exception in 2/files/download: {".tag":"path","path":"not_found"}

Здравко

Hi @BradHenderson,

As the error message shows, you have referred non existing file/folder. There is variety of reasons such thing to happen: you have deleted your file/folder unintentionally and as a result path doesn't exists or used id changed, you have selected different namespace (in case of team account), etc.

Good way, to check what's going on, is looking for the file/folder you're interested in starting from the account/namespace root (empty path). In a recursive way step to the target place and see where your expectation differs with the reality. 😉

Hope this gives direction.

BradHenderson

Thanks you Здравко,

I think I don't fully understand how to do what I want to do. I thought I could just load the app onto a different device provide the app with correct token and Dropbox would give access to the new device. The folder and file are definitely still there as I can view them from my desktop app. The original device (Tablet1) still can access the folder and file. So I am guessing the issue must be a user id problem. How do I tell Dropbox to allow this device to access the folder?

Thank you for you help

Brad

Здравко

@BradHenderson wrote:
... I thought I could just load the app onto a different device provide the app with correct token and Dropbox would give access to the new device. ...

Hope it's a bit more clear now.

BradHenderson

Thanks again Здравко,

Once again you have helped me by going back to basics. I recently added a new keyboard and when I added it to the system I didn't realise it was set to "International" and had added an umlaut to the letter A in the directory path. When I went back as you suggested to reduce the path step I found that the path should be "/Files/ALBG/" but was actually "/Files/ÄLBG/". My eyesight not being the best I didn't notice this difference. I don't know how this character Ä was even produced. Thanks again for your help it is greatly appreciated.

Brad