Previously, I have a set of Google Drive API code, which works fine in the following scenarios
Note: please do not treat this as an "official answer from Google". Although I work at Google, I don't work on the Drive API.
I've reproduced the problem, and reported it to the Drive API team, who may be able to provide more details. In the meantime, one workaround I've found is to remove the
setNewRevision(false)
part of your update
call on line 1414. That's not an ideal workaround as it means you'll get a new revision for each update, which will use up storage quota. However, it does seem to avoid the problem you've seen.