ID 401450 - To Editorial: AAF's and PDF's are not being copied to the publish directory when on a network share

Problem summary
During publishes the AAF and PDF are initially stored in the local assets folder (the asset cache). Once they have been created they are then moved to the designated publish directory as set in the Preference, Show settings or Studio settings. The issue is that these files can't be moved, they need to be copied. This is preventing the AAF and PDF files from being on the network drives when publishing to Editorial. This includes publishes to Avid and Premiere.  

Customer reported version

Customer reported platform
10.13

Steps to reproduce

1. Set the publish directory to any storage an a network (non-local).  
2. Publish to Premiere with 'contact sheet' enabled. Or publish to Avid (with/without contact sheet produces different errors.  

Expected behaviour
Publishing to Editorial should also be successful, with or without a contact sheet. 

Actual behaviour
Publishing to Editorial with a contact sheet will fail. Publishing an AAF to Avid (without a contact sheet) will show a publish successful message on the UI, but show a publish failed message in the client console. The AAF will not be generated. See screenshots for errors

No errors on the server side. 

Workaround
Copying the AAF and PDF during the publish will resolve the problem. 

Reproduced by QA
Tested on Mac 10.14.3 and Windows 10. Flix pipeline, 6.0.1 #28.