This is an inconsistent error that we’re having problems specifically reproducing (QA, Devs and myself can set up games similarly and not encounter the error), however, we know what it is generally attributed to and we are working on fixing that.
Hopefully by fixing one thing, we’ll solve this issue as well.
ETA currently unknown but it is actively being worked on as a priority.