java - Google Drive API List Files bug and Web Link bug -

I have an Android phone app prototype that can be used to sync the database sitting in the phone using the Google Phone Public Web Link feature Has been an XML file for

For the past 3 weeks now, two important issues have emerged that according to the stability, I will list them and you will be able to tell people of your temporary patch to solve it.

(1) Around the time of March 27, 2014, when the Java API, the number of items per page and the exponential back-off in the query again in case of failures with the exponential back-off in max, as It has been seen here: for some test sites, but not all (most Canadians did not have an impact on sites, and very few U.S. sites were unaffected by the south near NYC), resulting in 500 internal server error E In addition to more than one patch, among other things, was to slow the rate of inquiries per user per minute, and up went the set API Console query rate has been raised 10 times. All this has not been of any use. The final patch was to extract multiple file lists with a cue filter set with a basic identifier ID, and instead to use children's questions, Google Drive is now able to rebuild a given tree of files within a user Remember, the important thing is that this code works directly for 6 months, and the failure has started in the test sites around the above mentioned date. A hypothesis that I believed could not have been able to work anymore with many parent ID filters.

Trashed = false and hidden = false and ('parent ID 1') can anybody correlate their own experiences with me on this?

'PARENTID2' in parent or parent or 'PARENTID3' in parent)

... where PARENTIDx is the given parent ID string Note that this query string can have up to 10 different original IDs at a time.

The function was also called with a limit in some cases, failure cases to downgrade this maximum number 1000 items with backup in

(2) April 22, 2014, 5:00 AM Eastern Time, Google Drive went to the folder across the web All test site. I uploaded the drive to some affected test sites Timestamp of checked files is checked, and timestamps were updated correctly at the right time during about 2 minutes of tolerance. However, the XML file is being brought in the form of a public link, indicating that the old version is received from 22 April, 5:00 am, or earlier, instead, this is the first time I have seen it since We have consistently tested the Disk Public Web Link feature (since January 2014). I know someone (probably a Google engineer), who will be able to make it clear, if possible, want to input somebody ... In any case, damage control is now necessary, so I use it either The HTML Drive API will change our entire database hosting strategy to circumvent this problem, or just another provider, which provides better stability, please advise ...

(Update for ITM2): It appears that the timestamp stored in the metadata is correct, but the contents of the file remain obsolete, thus the use of the HTML drive API is a Controversial point to try to remove some important files (going into the trash) triggers the rebirth of the folder containing .xml by app, but it appears that the content of rebuilt files She is old. Note that the regular user interface is used to remove and upload files for the drive to still work.

It seems that the only way to restore proper drive behavior is, in the trash.

(Update again for ITEM): I brought this question to:

Thanks for the report .. 1 seems to be a bug with the new implementation that is being issued to users. We will fix it. (Note that using "or" is a non-documentary feature, but it was used to work.)

I do not completely follow # 2, but maybe a Different questions are worth asking.