{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 成全新的幸福 的问题《File Revisions suspect behavior?》','https://www.manongdao.com/q-1281358.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
New problem seems to have appeared today with GoogleDrive non-native file revisions.
Been successfully updating existing documents in a GoogleDrive account for months now from a C# app via the GoogleDrive API - some files have 40, 60 and even over 100 revisions just fine.
Today when an update is done with a request for new revision and pinned, the existing revision is overwritten and no new revision is created. Seems to only be on existing, multi-revision files.
Can create a new file and update again and again just fine.
Also tried it through the Google Drive web app instead of the API and getting the same behaviour.
New files can have multiple revisions added to them successfully - existing files do not get new revisions, only replaces head revision instead.