File Directory not found

In the Backendless console, I have a directory with nothing in it and I’m getting the following error:

{“code”:6007,“message”:“The specified resource was not found”}The Date/Time on the directory is off which reads: 12/31/1969, 7:00:00 PM

Hi Roy!
Please provide your URL to this directory.

Regards,
Kate.

https://develop.backendless.com/console/85640F83-1394-1E16-FFF8-1DCE458CAE00/appversion/5768D68A-018C-5DB4-FFF1-4AC2FB600700/xdecqvpkepuffkarqrblhazxtulsgjvdmetc/files/view/Hints

How you get such url?

From selection in the browser and copy/paste

It is not correct way to get access to file/folder.
You can get access to files via public url, files listing api or management console api.

I understand but for some reason in the browser this directory is handled much different than the others. For one, when hovering over the directory with the mouse, the context URL link is displayed for this directory at the bottom of the Browser. No other directory is that I have acts like that. Also, I noticed that this directory is my last directory in the File listing. All other directory are being sorted based on the directory name and this one isn’t.

I wanted to let you know that today I selected the same directory I had this problem with and now it is displaying all my files as expected. Not sure what the problem was but…

This problem has been seen again.

The API steps I am performing are using the REST API:

  1. Upload file using the File Upload API
  2. Download the file using the Download API
  3. Delete the file using the Delete API.

This process has worked with no problems for a long time now until now. I don’t see how these steps could be influencing this behavior.

And what is exactly the problem? Which of the steps is causing an error? (1, 2 or 3?)

Regards,
Mark

All the steps and API methods successful perform the action. At some point the directory I am using for these API’s becomes corrupted. I see this right now by viewing the directory in the Backendless Console.

I will put a break point at each step of the API calls and see if I see an error but I haven’t seen one.

I was attempting to delete the directory I was using from the Backendless console but I’m getting an error. The error is: File or Directory not found.

I am trying to understand at what point it becomes corrupted.

Does the step 3 complete?

Do you see the directory in Backendless Console after step 3 is complete?

Does the directory contain any other files after step 3 is complete?

From what I am seeing now, steps 1 completes with no problems. Step 2 & 3 fails at some point half way in the file listing. I might have 20 files , it probably fails around file 10.

I’m in the processing of debugging this at each point and trying to get a handle on exactly where.

So far, I’ve run 3 tests and haven’t seen the problem. Will run a few more… and get back with you