Google Drive SDK Push Notifications, receiving wrong changes id

Question

When I subscribe to all changes of my Drive account, sometimes I receive changes with wrong id. According to my observations changes of specific file are aggregated in last change with some time period.

For example: If I change file in my drive and if I have received 3 notifications with ids: "#21, #22, #23", I expected that I can get change of "#23", if there is no more changes to that file. But sometimes I receive last change with id greater than it exists. When I use API changes list, I get lastlargestChangeId = receivedChangesId - 1.

I have tested it with google examples and I get the same results:

push notifications test

{"notification_id": "xxxxxxxxxxx", "resource_state": "change", "expiration": "Mon, 07 Jul 2014 13:58:37 GMT", "self_link": "https://www.googleapis.com/drive/v2/changes/3387"}

{ "kind": "drive#changeList", "etag": "xxxxxxxxxxx", "selfLink": ".../changes?startChangeId=3340", "largestChangeId": "3386", "items": [ ... ] }

Am I wrong?

Answer 1

It seems that Google categorized it as a bug: https://code.google.com/a/google.com/p/apps-api-issues/issues/detail?id=3706

Star it so Google can prioritize it.