Forums
(@marcool04)
4 years, 9 months ago
This is definitely still a problem, even with the purported fix in v2.2. I also solved it by reverting to 2.1.3. Would be happy to help if any more debugging information is needed.