ID 486449 - Invalid path for Client Temp Directory will result in failed publishes if the Generate Contact Sheet checkbox is ticked

Follow

Problem summary
Changing the Temp Directory in Preferences > Advanced to an invalid path will result in failed publishes if the Generate Contact Sheet checkbox is ticked. PDFs requested separately from the publish, via the Export functionality will generate successfully.

Customer reported version
Flix 6.3.5

Steps to reproduce
1a) Go to Preferences > Advanced and change the Temp Directory path to somewhere you are aware will not be valid, for example /Users/asdf!ghjkl;.
OR
1b) Go to Preferences > Advanced and change the Temp Directory path to a valid one, but where Flix would be required to automatically generate a new directory. For example /Users/Katie/TEST, where /Users/Katie exists and TEST doesn't.

2) Go to any unpublished sequence revision, and publish it making sure the Generate Contact Sheet checkbox is ticked. Both publishing to Avid and to Premiere will fail, with slightly different errors, but for the same reason (Contact Sheet failing to generate).

Expected behaviour
Flix should check that the new path for the Temp Directory is valid. If it's not, the user needs to be notified immediately and the change should be disregarded. Should the path be valid but the directory not exist, Flix should be able to create one when necessary (for example when the Contact Sheet generation during the publish is requested).

Actual behaviour
The whole publish will fail, because the Contact Sheet couldn't be generated. The errors shown in the Client will be different depending on whether the publish was to Avid or to Premiere:

Premiere publish


Avid publish
​​

Workaround
Go to ​Preferences > Advanced and change the path for the Temp Directory to a valid one. 
If you are not sure what to set the path to and can't wait for IT to help, you can export the PDF separately, before publishing.

Reproduced by support
This bug has been reproduced in:
6.3.6 - macOS Client - Windows Client
6.1.2 - macOS Client

Earliest version tested
6.1.2 - This issue appears to be in all versions of the product

    We're sorry to hear that

    Please tell us why