Unfortunately not – In my case it looks like it was caused by the WordPress update which broke things for a lot of users then they must have released some sort of patch which fixed it. I still have the same console error I don’t actually think it’s relevant
