Forums
(@brentfincham)
8 years, 7 months ago
Had this same issue. Today’s patch (v1.35.6) fixed it right up. Thanks Richard!