Drive API bug: no 404 response on drive.children.list/drive.files.list
GoogleCodeExporter opened this issue · comments
I realise this is not a bug directly with the Obj-c client itself and the
server API but I cannot find a better place to report this.
What steps will reproduce the problem?
1. Create folder with files
2. Permanently delete folder with files
3. Perform drive.children.list or drive.files.list q:id in parents
What is the expected output? What do you see instead?
Expected output should be a 404 error, and was until last week
instead received, note the missing results collection:
The library interprets this as 0 children
id = "gtl_19";
result = {
etag = "\"maCRbN5nR56FjQPLihEiz9nzpho/vyGp6PvFo4RvsFtPoIWeCReyIC8\"";
kind = "drive#childList";
};
What version of the product are you using? On what operating system?
OSX/iOS
Please provide any additional information below.
This is new behaviour as until recently my tests successfully forced a 404
error whereas now they fail with 0 results.
Original issue reported on code.google.com by amcca...@gmail.com
on 18 Nov 2013 at 10:31
Google Drive API engineers do not monitor this issues list. Please try posting
via https://developers.google.com/drive/support
Original comment by grobb...@google.com
on 19 Nov 2013 at 1:44
- Changed state: Invalid