If you’ve rolled back to v6 and are still seeing this issue, it is unlikely to be related to v7. Please do submit a bug report with reproducible steps so that our team can investigate!