Google Drive API JSON reponse for changes returns bad count of items for the first page

Google Drive API JSON reponse for changes returns bad count of items for the first page. It is Google API issue. User of camel google-drive component can be confused because of this unexpected behaviour. This problem is connected definitely with changes and maybe with more objects, but it is not connected with files.

Try the following command:

GET https://www.googleapis.com/drive/v2/changes?maxResults=3&access_token=ACCESS_TOKEN

=> It returns only 2 items even if there are more items available
(We will receive nextPageToken for next page of items)

GET https://www.googleapis.com/drive/v2/changes?maxResults=3&pageToken=TOKEN&access_token=ACCESS_TOKEN

=> Returns 3 items if there is more then 2 items available...