That would make sense. The error is caused during the initialisation of comms which happens before logging is disabled/enabled. It is possible to prevent the error from happening by manually removing the logging functionality but we are ‘today’ looking for an alternative which would allow the logging to be used with unity.