Documents updated in Google Drive are send with 0 byte to CMIS Output Connector

When dealing with migration process, like when using the CMIS Output Connector to ingest content into an ECM (Alfresco in my case), I noticed that when a document is updated inside Google Drive, the engine is able to detect the change and put it into the queue to be updated into the output.

By using the CMIS Output Connector, the document is versioned into Alfresco, but this new version is always created as a 0 byte file.

I configured the issue as a Framework core because I am still not sure who is causing the problem, if the GoogleDrive Connector or the CMIS Output Connector